Automating DNS Record Creation with Kubernetes and Cloudflare
🖥️ Why bother? Automating DNS record creation sounds fancy, sounds cool even, but what does it actually get you? When you’re running a Kubernetes cluster, one of the tools you really can’t do without is the ingress controller. It acts as a reverse proxy, which means it’s the one deciding where incoming HTTP/S traffic actually goes. graph LR subgraph DNS Entries A1[one.example.org] A2[two.example.org] A3[three.example.org] end RP[Reverse Proxy] subgraph Backends S1[Server One] S2[Server Two] S3[Server Three] end A1 --> RP A2 --> RP A3 --> RP RP --> S1 RP --> S2 RP --> S3 Ok, so if my reverse proxy already redirects traffic to the right application based on the DNS entry, why not just use a wildcard? ...