From 46dd6d2e2bb24a965a83a139671140c3bcd413d5 Mon Sep 17 00:00:00 2001 From: Michel Loiseleur <97035654+mloiseleur@users.noreply.github.com> Date: Tue, 9 Apr 2024 11:06:20 +0200 Subject: [PATCH] doc: advertise current plan on providers (#4365) * doc: advertise current plan on providers * Update README.md Co-authored-by: Raffaele Di Fazio * Update README.md --------- Co-authored-by: Raffaele Di Fazio --- README.md | 12 ++++-------- 1 file changed, 4 insertions(+), 8 deletions(-) diff --git a/README.md b/README.md index 272fad997b..641f31dd7a 100644 --- a/README.md +++ b/README.md @@ -88,15 +88,11 @@ Known providers using webhooks: | Netcup | https://github.com/mrueg/external-dns-netcup-webhook | | STACKIT | https://github.com/stackitcloud/external-dns-stackit-webhook | -## Status of providers +## Status of in-tree providers -ExternalDNS supports multiple DNS providers which have been implemented by the [ExternalDNS contributors](https://github.com/kubernetes-sigs/external-dns/graphs/contributors). Maintaining all of those in a central repository is a challenge and we have limited resources to test changes. This means that it is very hard to test all providers for possible regressions and, as written in the [Contributing](#Contributing) section, we encourage contributors to step in as maintainers for the individual providers and help by testing the integrations. +ExternalDNS supports multiple DNS providers which have been implemented by the [ExternalDNS contributors](https://github.com/kubernetes-sigs/external-dns/graphs/contributors). Maintaining all of those in a central repository is a challenge, which introduces lots of toil and potential risks. -End-to-end testing of ExternalDNS is currently -[performed](https://github.com/zalando-incubator/kubernetes-on-aws/blob/dev/test/e2e/external_dns.go) -in the separate -[kubernetes-on-aws](https://github.com/zalando-incubator/kubernetes-on-aws) -repository. +This mean that `external-dns` has begun the process to move providers out of tree. See #4347 for more details. Those who are interested can create a webhook provider based on an _in-tree_ provider and after submit a PR to reference it here. We define the following stability levels for providers: @@ -112,7 +108,7 @@ The following table clarifies the current status of the providers according to t | AWS Route 53 | Stable | | | AWS Cloud Map | Beta | | | Akamai Edge DNS | Beta | | -| AzureDNS | Beta | | +| AzureDNS | Stable | | | BlueCat | Alpha | @seanmalloy @vinny-sabatini | | Civo | Alpha | @alejandrojnm | | CloudFlare | Beta | |