Merge pull request #49017 from aivantsov/patch-1

Simplify reflecting the CoreDNS changes after updating the CoreDNS Deployment and Service

Author: k8s-ci-robot

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

@@ -202,22 +202,12 @@ kubectl edit service -n kube-system kube-dns
 
 #### Reflecting the CoreDNS changes
 
-Once the CoreDNS changes are applied you can delete the CoreDNS Pods:
-
-Obtain the Pod names:
-
-```shell
-kubectl get po -n kube-system | grep coredns
-```
-
-Delete a Pod with:
+Once the CoreDNS changes are applied you can restart the CoreDNS deployment:
 
 ```shell
-kubectl delete po -n kube-system <pod-name>
+kubectl rollout restart deployment -n kube-system coredns
 ```
 
-New Pods with the updated CoreDNS configuration will be created.
-
 {{< note >}}
 kubeadm does not allow CoreDNS configuration during cluster creation and upgrade.
 This means that if you execute `kubeadm upgrade apply`, your changes to the CoreDNS