Graduate CoreDNS to GA
Graduate CoreDNS to GA
Table of Contents
CoreDNS is sister CNCF project and is the successor to SkyDNS, on which kube-dns is based. It is a flexible, extensible
authoritative DNS server and directly integrates with the Kubernetes API. It can serve as cluster DNS,
complying with the dns spec. As an independent project,
it is more actively developed than kube-dns and offers performance and functionality beyond what kube-dns has. For more details, see the introductory presentation, or coredns.io, or the CNCF webinar.
Currently, we are following the road-map defined here. CoreDNS is Beta in Kubernetes v1.10, which can be installed as an alternate to kube-dns.
The purpose of this proposal is to graduate CoreDNS to GA.
- CoreDNS is more flexible and extensible than kube-dns.
- CoreDNS is easily extensible and maintainable using a plugin architecture.
- CoreDNS has fewer moving parts than kube-dns, taking advantage of the plugin architecture, making it a single executable and single process.
- It is written in Go, making it memory-safe (kube-dns includes dnsmasq which is not).
- CoreDNS has better performance than kube-dns in terms of greater QPS, lower latency, and lower memory consumption.
- Bump up CoreDNS to be GA.
- Make CoreDNS available as an image in a Kubernetes repository (To Be Defined) and ensure a workflow/process to update the CoreDNS versions in the future.
May be deferred to next KEP if goal not achieved in time.
- Provide a kube-dns to CoreDNS upgrade path with configuration translation in
- Provide a CoreDNS to CoreDNS upgrade path in
- Translation of CoreDNS ConfigMap back to kube-dns (i.e., downgrade).
- Translation configuration of kube-dns to equivalent CoreDNS that is defined outside of the kube-dns ConfigMap. For example, modifications to the manifest or
- Fate of kube-dns in future releases, i.e. deprecation path.
- Making CoreDNS the default in every installer.
The proposed solution is to enable the selection of CoreDNS as a GA cluster service discovery DNS for Kubernetes.
Some of the most used deployment tools have been upgraded by the CoreDNS team, in cooperation of the owners of these tools, to be able to deploy CoreDNS:
For other tools, each maintainer would have to add the upgrade to CoreDNS.
CoreDNS supports all functionality of kube-dns and also addresses several use-cases kube-dns lacks. Some of the Use Cases are as follows:
- Supporting Autopath, which reduces the high query load caused by the long DNS search path in Kubernetes.
- Making an alias for an external name #39792
By default, the user experience would be unchanged. For more advanced uses, existing users would need to modify the ConfigMap that contains the CoreDNS configuration file.
Since CoreDNS has more supporting features than kube-dns, there will be no path to retain the CoreDNS configuration in case a user wants to switch to kube-dns.
The CoreDNS configuration file is called a
Corefile and syntactically is the same as a Caddyfile. The file consists of multiple stanzas called server blocks.
Each of these represents a set of zones for which that server block should respond, along with the list of plugins to apply to a given request. More details on this can be found in the
Corefile Explained and How Queries Are Processed blog entries.
The following can be expected when CoreDNS is graduated to GA.
- The CoreDNS feature-gates flag will be marked as GA.
- As Kubeadm maintainers chose to deploy CoreDNS as the default Cluster DNS for Kubernetes 1.11:
- CoreDNS will be installed by default in a fresh install of Kubernetes via kubeadm.
- For users upgrading Kubernetes via kubeadm, it will install CoreDNS by default whether the user had kube-dns or CoreDNS in a previous kubernetes version.
- In case a user wants to install kube-dns instead of CoreDNS, they have to set the feature-gate of CoreDNS to false.
- When choosing to install CoreDNS, the configmap of a previously installed kube-dns will be automatically translated to the equivalent CoreDNS configmap.
- CoreDNS will be installed when the environment variable
CLUSTER_DNS_CORE_DNS is set to
true. The default value is
- CoreDNS to be an option in the add-on manager, with CoreDNS disabled by default.
- Verify that all e2e conformance and DNS related tests (xxx-kubernetes-e2e-gce, ci-kubernetes-e2e-gce-gci-ci-master and filtered by
--ginkgo.skip=\\[Slow\\]|\\[Serial\\]|\\[Disruptive\\]|\\[Flaky\\]|\\[Feature:.+\\]) run successfully for CoreDNS.
None of the tests successful with Kube-DNS should be failing with CoreDNS.
- Add CoreDNS as part of the e2e Kubernetes scale runs and ensure tests are not failing.
- Extend perf-tests for CoreDNS.
- Add a dedicated DNS related tests in e2e scalability test [Feature:performance].