What problem does it solve? Manually creating and updating DNS records for Kubernetes Services, Ingresses, and Gateway API routes is error-prone and quickly drifts out of sync with the cluster. This Skill provides the operational knowledge to deploy and configure ExternalDNS so DNS records are created, updated, and owned automatically. ## Core Features & Use Cases - Source and Provider Configuration: Covers all supported sources (Ingress, Service, Gateway HTTPRoute/GRPCRoute/TLSRoute, Istio, CRD) and provider setup with a focus on Cloudflare API token authentication and proxy flags. - Ownership and Policy Management: Explains TXT registry ownership tracking, txtOwnerId, and sync policies (upsert-only, sync, create-only) to prevent accidental record deletion in shared zones. - Gateway API and RBAC Integration: Details the extra RBAC rules required for gateway-httproute sources and per-route annotation overrides for Cloudflare proxying and TTL. - Use Case: You expose a new application via a Cilium Gateway HTTPRoute and want its hostname to appear automatically in Cloudflare DNS with the proxy enabled, without touching the Cloudflare dashboard. ## Quick Start Ask the agent to configure ExternalDNS with the Cloudflare provider and gateway-httproute source so DNS records are created automatically for your HTTPRoute hostnames.