external-dns
Skill4 starsChanged 5 months agoMITView on GitHub
Use when working with ExternalDNS — synchronizing Kubernetes resources with DNS providers (Cloudflare). Covers providers, sources, registry, RBAC, Gateway API integration, Helm values. No CRDs.
In this repository74 other files it gives its agents.
- AGENTS.mdAGENTS.md
- atlasSkill
- cert-managerSkill
- cilium-gatewaySkill
- cilium-networkSkill
- cnpgSkill
- dragonflySkill
- external-secretsSkill
- flaggerSkill
- fluxSkill
- gitea-apiSkill
- gitea-registrySkill
- gitea-runnerSkill
- giteaSkill
- gitea-teaSkill
- gitea-webhooksSkill
- harbor-apiSkill
- harbor-helmSkill
- harborSkill
- harbor-terraformSkill
- helm-chartSkill
- helm-opsSkill
- helmSkill
- higress-helmSkill
- higress-operatorSkill
- higressSkill
- kserve-helmSkill
- kserve-operatorSkill
- kserveSkill
- kubeflow-pipelinesSkill
- kubeflowSkill
- kubeflow-trainerSkill
- kubeflow-training-operatorSkill
- mariadb-helmSkill
- mariadb-operatorSkill
- mariadbSkill
- netbird-cliSkill
- netbird-operatorSkill
- netbird-serverSkill
- netbirdSkill
- netbird-terraformSkill
- nextcloud-apiSkill
- nextcloud-helmSkill
- nextcloudSkill
- nvidia-device-pluginSkill
- rook-ceph-operatorSkill
- rook-cephSkill
- rook-ceph-toolboxSkill
- sealed-secretsSkill
- stakater-reloaderSkill
- tailscaleSkill
- tailscale-talosSkill
- talosconfigSkill
- talosctlSkill
- talosSkill
- talos-terraformSkill
- tekton-operatorSkill
- tekton-pacSkill
- tekton-pipelinesSkill
- tektonSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 180
upsert-onlydoesn't clean up stale records: When an Ingress/HTTPRoute is deleted, its DNS record persists. - Very specific: line 185
Multiple TXT owner IDs on same zone: If two ExternalDNS instances manage the same zone with different txtOwnerId, they can coexist.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
ExternalDNS
Overview
ExternalDNS synchronizes exposed Kubernetes Services, Ingresses, and Gateway API routes with DNS providers. It watches resources via the K8s watch API and creates/updates/deletes DNS records to match.
No CRDs. Controlled via CLI flags, sources, and provider-specific config.
Latest: chart 1.21.1, app v0.21.0.
Architecture
K8s Sources (Ingress, HTTPRoute, Service...)
→ ExternalDNS watches for changes
→ Resolves to DNS endpoints
→ Creates/updates/deletes DNS records (Cloudflare, Route53, etc.)
→ Registry (TXT records) tracks ownershipSources
ExternalDNS queries one or more source types for DNS endpoints:
| Source | Flag | Supported |
| Ingress | --source=ingress | ✅ |
| Service (LoadBalancer) | --source=service | ✅ (no NodePort) |
| Gateway HTTPRoute | --source=gateway-httproute | ✅ |
| Gateway GRPCRoute | --source=gateway-grpcroute | ✅ |
| Gateway TLSRoute | --source=gateway-tlsroute | ✅ (v1alpha2) |
| Gateway TCPRoute | --source=gateway-tcproute | ✅ (experimental) |
| Gateway UDPRoute | --source=gateway-udproute | ✅ (experimental) |
| Istio Gateway | --source=istio-gateway | ✅ |
| Istio VirtualService | --source=istio-virtualservice | ✅ |
| CRD | --source=crd | ✅ (externaldns.k8s.io/v1alpha1) |
| Node | --source=node | ✅ |
| Pod | --source=pod | ✅ |
| OpenShift Route | --source=openshift-route | ✅ |
| Contour HTTPProxy | --source=contour-httpproxy | ✅ |
| Traefik Proxy | --source=traefik-proxy | ✅ |
Deployed sources: ingress, gateway-httproute.
Providers
ExternalDNS supports 25+ providers. Deployed: Cloudflare.
Cloudflare
Auth via API token (env var CF_API_TOKEN). Example values:
provider:
name: cloudflare
env:
- name: CF_API_TOKEN
valueFrom:
secretKeyRef:
name: cloudflare-credentials
key: api-token
extraArgs:
- --cloudflare-proxiedCloudflare-specific flags:
| Flag | Description |
--cloudflare-proxied | Enable Cloudflare proxy (orange cloud) — CDN, DDoS protection, SSL |
--cloudflare-dns-records-per-page=N | Records per page (default 100, max 5000) |
--cloudflare-custom-hostnames | Enable Cloudflare for SaaS Custom Hostnames |
--cloudflare-regional-services | Restrict HTTPS decryption to specific regions |
--cloudflare-region-key | Region key for regional services |
--cloudflare-record-comment | Add comment to provisioned records (≤100/≤500 chars) |
Registry & Policy
Controls how ExternalDNS tracks ownership of records:
registry: txt # Use TXT records to track ownership
txtOwnerId: my-cluster # Owner identifier in TXT record
policy: upsert-only # Only create/update, never delete| Registry | Description |
txt | TXT records with owner ID (prevents overwriting records from other sources) |
aws | AWS Route53 tag-based (provider-specific) |
noop | No ownership tracking |
| Policy | Description |
upsert-only | Create and update only (safe for shared zones) |
sync | Full sync — create, update, delete (can delete external records) |
create-only | Only create, never update or delete |
Domain & Ownership Filtering
domainFilters:
- example.com # Only manage records in this zone
excludeDomains: [] # Exclude specific domains
zoneIdFilters: [] # Limit to specific zone IDs
annotationFilter: "" # Filter resources by annotation
labelFilter: "" # Filter resources by labelGateway API Integration
ExternalDNS reads hostnames from Gateway API HTTPRoute/GRPCRoute resources:
sources:
- gateway-httproute
- gateway-grpcrouteRBAC for Gateway sources requires additional permissions:
rbac:
extraRules:
- apiGroups: ["gateway.networking.k8s.io"]
resources: ["httproutes", "gateways"]
verbs: ["get", "watch", "list"]HTTPRoute annotations for per-route overrides:
metadata:
annotations:
external-dns.alpha.kubernetes.io/cloudflare-proxied: "true"
external-dns.alpha.kubernetes.io/ttl: "300"Deployment (Flux HelmRelease)
apiVersion: helm.toolkit.fluxcd.io/v2
kind: HelmRelease
spec:
chart:
spec:
chart: external-dns
sourceRef:
kind: HelmRepository
name: external-dns
version: 1.21.1Helm Values
| Value | Default | Description |
provider.name | aws | DNS provider (cloudflare, google, aws, azure, etc.) |
sources | [service, ingress] | Resources to watch (ingress, gateway-httproute, service, etc.) |
domainFilters | [] | Limit to specific DNS zones |
policy | upsert-only | Sync policy (upsert-only, sync, create-only) |
registry | txt | Ownership registry (txt, aws, noop) |
txtOwnerId | — | Owner identifier for TXT registry |
interval | 1m | Sync interval |
logLevel | info | Log verbosity |
rbac.create | true | Create ClusterRole |
rbac.extraRules | [] | Additional RBAC rules (e.g. for Gateway API) |
nodeSelector | {} | Node selector |
tolerations | [] | Pod tolerations |
extraArgs | [] | Additional CLI args |
Common Mistakes
- Missing RBAC for Gateway sources. Without
rbac.extraRules, gateway-httproute source returns no endpoints. Bothhttproutesandgatewaysresources must be listed. upsert-onlydoesn't clean up stale records. When an Ingress/HTTPRoute is deleted, its DNS record persists. Usesyncpolicy or manual cleanup.- Cloudflare API token needs specific permissions. Requires
Zone:DNS:Editfor the target zone. A token with onlyZone:Readwill fail silently. --cloudflare-proxiedis a global flag. To proxy only specific records, omit the global flag and use theexternal-dns.alpha.kubernetes.io/cloudflare-proxied: "true"annotation per resource.- Domain filter is a suffix match.
example.commatchesapp.example.combut NOTexample.com.app.com. Add trailing dot if needed. - NodePort services not supported with
source=service. Only LoadBalancer services are detected. - Multiple TXT owner IDs on same zone. If two ExternalDNS instances manage the same zone with different
txtOwnerId, they can coexist. Records with unknown owner ID are left untouched byupsert-only.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

