All add-ons · DNS

Is external-dns compatible with Kubernetes 1.37?

Synchronizes Kubernetes Services and Ingresses to DNS providers. The README publishes a version-range compatibility table.

Kubernetes 1.37, current tracked release 0.18:

Applies to ExternalDNS ≥ 0.18. Every minor in this grid is a yes cell. Kubernetes 1.19–1.20 and ≤ 1.18 are no cells and are outside this grid.

README Kubernetes version compatibility: ExternalDNS ≥ 0.18 supports Kubernetes 1.21, Kubernetes ≥ 1.22 and ≤ 1.32, and Kubernetes ≥ 1.33. It does not support Kubernetes 1.19–1.20 or ≤ 1.18. ExternalDNS ≥ 0.10 and ≤ 0.17 supports 1.19 through 1.32 and does not support ≥ 1.33.

Version grid

external-dns 1.311.321.331.341.351.361.37
0.18 · current SupportedSupportedSupportedSupportedSupportedSupportedSupported
0.10–0.17 SupportedSupportedNot supportedNot supportedNot supportedNot supportedNot supported

Empty-looking “not in the published matrix” cells were not listed by the project. They are not a guess that the combination fails.

Notes

Breaking changes called out in the README: v0.10.0 switched Ingress to networking.k8s.io; v0.18.0 switched to EndpointSlices; v0.19.0 stopped exposing internal IPv6 by default. Helm chart name is external-dns.

Sources

Last checked 2026-11-15. Latest GitHub release v0.24.0 (opens in a new tab) (2026-10-23).

Project site: https://github.com/kubernetes-sigs/external-dns (opens in a new tab)

Managed Kubernetes end of support

Addon compatibility is not the same as the platform’s support window. End-of-support dates for the managed services are on EOL Radar: Amazon EKS (opens in a new tab), Azure AKS (opens in a new tab), Google Kubernetes Engine (opens in a new tab).

JSON for this add-on · Check a helm list