Repository navigation
Feature Request: Expose all upstream ExternalDNS providers in Operator API (CloudFlare, DigitalOcean, Linode, etc.) #298
Description
Description
The ExternalDNS Operator currently only exposes a limited subset of DNS providers in its CRD API, despite the underlying ExternalDNS binary (v0.19.0) supporting 30+ providers. This limitation prevents users from leveraging the full capabilities of upstream ExternalDNS.
Current State
Operator Version: v1.3.1
Underlying ExternalDNS Version: ~v0.19.0 (binary dated 2024-09-08)
API Version: externaldns.olm.openshift.io/v1beta1
Currently Exposed Providers (in Operator API)
The ExternalDNS CRD currently only supports configuration for:
- AWS (Route53)
- Azure DNS
- BlueCat
- Google Cloud DNS
- Infoblox
Reference: spec.provider field in the CRD
Upstream Supported Providers (in binary)
The ExternalDNS binary included in the operator supports 30+ providers, including:
Missing Popular Providers:
- CloudFlare
- DigitalOcean
- Linode
- OVH
- Akamai
- DNSimple
- Vultr
- Scaleway
- TransIP
- GoDaddy
- Gandi
- NS1
- PowerDNS
- Pi-hole
- RFC2136 (generic DNS UPDATE)
- Webhook (custom providers)
- And many more...
Reacted by Fabian Becker and yoav-katz
Activity
openshift-bot commentedon Feb 4, 2026
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting
/remove-lifecycle stale.Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting
/lifecycle frozen.If this issue is safe to close now please do so with
/close./lifecycle stale
StringKe commentedon Feb 4, 2026
/remove-lifecycle stale
Dave-c-Ross commentedon Mar 17, 2026
+1
openshift-ci commentedon Jun 16, 2026
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting
/remove-lifecycle stale.Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting
/lifecycle frozen.If this issue is safe to close now please do so with
/close./lifecycle stale
StringKe commentedon Jun 17, 2026
/remove-lifecycle stale
openshift-ci commentedon Sep 16, 2026
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting
/remove-lifecycle stale.Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting
/lifecycle frozen.If this issue is safe to close now please do so with
/close./lifecycle stale
StringKe commentedon Sep 16, 2026
/lifecycle stale
StringKe commentedon Sep 16, 2026
/remove-lifecycle stale