Setting Up External DNS with Cloudflare on a Local Kubernetes Cluster

This installment of a Kubernetes series explains how to deploy External DNS to automate DNS record management on a local cluster. The author uses Cloudflare as the DNS provider and follows declarative GitOps practices with Flux. The process starts by generating a zone-scoped Cloudflare API token and storing its credentials in a Kubernetes secret, which is encrypted with SOPS before being committed to Git. The External DNS deployment is then defined through a ServiceAccount, a read-only ClusterRole and binding, and a Deployment that watches ingresses and syncs records to Cloudflare. The article notes that the setup builds on earlier steps for routing external traffic to the cluster so it can be reached via a public IP.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in