From 3e9a73f7c28d76280c76d74dc3e58213715b99b4 Mon Sep 17 00:00:00 2001 From: Sandeep Rajan Date: Fri, 5 Mar 2021 12:12:27 -0500 Subject: [PATCH] move kube-dns remove statement to the end --- .../reference/setup-tools/kubeadm/implementation-details.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/content/en/docs/reference/setup-tools/kubeadm/implementation-details.md b/content/en/docs/reference/setup-tools/kubeadm/implementation-details.md index 026e24f2ed..420f6edcac 100644 --- a/content/en/docs/reference/setup-tools/kubeadm/implementation-details.md +++ b/content/en/docs/reference/setup-tools/kubeadm/implementation-details.md @@ -436,13 +436,15 @@ A ServiceAccount for `kube-proxy` is created in the `kube-system` namespace; the #### DNS -- In Kubernetes version 1.21 kube-dns usage with kubeadm has been removed - The CoreDNS service is named `kube-dns`. This is done to prevent any interruption in service when the user is switching the cluster DNS from kube-dns to CoreDNS the `--config` method described [here](/docs/reference/setup-tools/kubeadm/kubeadm-init-phase/#cmd-phase-addon) - A ServiceAccount for CoreDNS is created in the `kube-system` namespace. - The `coredns` ServiceAccount is bound to the privileges in the `system:coredns` ClusterRole +- In Kubernetes version 1.21, support for using `kube-dns` with kubeadm is removed. +You can use CoreDNS with kubeadm even when the related Service is named `kube-dns`. + ## kubeadm join phases internal design Similarly to `kubeadm init`, also `kubeadm join` internal workflow consists of a sequence of atomic work tasks to perform.