Skip to content

Commit edc4dc7

Browse files
authored
Restart CoreDNS deployment to reflect configuration changes
1 parent b0e6a79 commit edc4dc7

File tree

1 file changed

+2
-4
lines changed

1 file changed

+2
-4
lines changed

content/en/docs/tasks/administer-cluster/kubeadm/kubeadm-reconfigure.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -202,14 +202,12 @@ kubectl edit service -n kube-system kube-dns
202202

203203
#### Reflecting the CoreDNS changes
204204

205-
Once the CoreDNS changes are applied you can delete the CoreDNS Pods:
205+
Once the CoreDNS changes are applied you can restart the CoreDNS deployment:
206206

207207
```shell
208-
kubectl delete po -n kube-system -l k8s-app=kube-dns
208+
kubectl rollout restart deployment -n kube-system coredns
209209
```
210210

211-
New Pods with the updated CoreDNS configuration will be created.
212-
213211
{{< note >}}
214212
kubeadm does not allow CoreDNS configuration during cluster creation and upgrade.
215213
This means that if you execute `kubeadm upgrade apply`, your changes to the CoreDNS

0 commit comments

Comments
 (0)