move kube-dns remove statement to the end
This commit is contained in:
@@ -436,13 +436,15 @@ A ServiceAccount for `kube-proxy` is created in the `kube-system` namespace; the
|
|||||||
|
|
||||||
#### DNS
|
#### 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
|
- 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
|
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)
|
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.
|
- A ServiceAccount for CoreDNS is created in the `kube-system` namespace.
|
||||||
- The `coredns` ServiceAccount is bound to the privileges in the `system:coredns` ClusterRole
|
- 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
|
## kubeadm join phases internal design
|
||||||
|
|
||||||
Similarly to `kubeadm init`, also `kubeadm join` internal workflow consists of a sequence of atomic work tasks to perform.
|
Similarly to `kubeadm init`, also `kubeadm join` internal workflow consists of a sequence of atomic work tasks to perform.
|
||||||
|
|||||||
Reference in New Issue
Block a user