From 4f189afac192a3127ca847252aac01a8e2c3e5b9 Mon Sep 17 00:00:00 2001 From: Jason Hu Date: Tue, 8 Jan 2019 20:08:18 +0800 Subject: [PATCH] Update dns-debugging-resolution.md (#12012) There is a document error in the subsection named "Check for Errors in the DNS pod" , where the pod selector should coredns but not kube-dns. --- .../docs/tasks/administer-cluster/dns-debugging-resolution.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/tasks/administer-cluster/dns-debugging-resolution.md b/content/en/docs/tasks/administer-cluster/dns-debugging-resolution.md index e0816f16cf..c521b0291d 100644 --- a/content/en/docs/tasks/administer-cluster/dns-debugging-resolution.md +++ b/content/en/docs/tasks/administer-cluster/dns-debugging-resolution.md @@ -122,7 +122,7 @@ Use `kubectl logs` command to see logs for the DNS containers. For CoreDNS: ```shell -for p in $(kubectl get pods --namespace=kube-system -l k8s-app=kube-dns -o name); do kubectl logs --namespace=kube-system $p; done +for p in $(kubectl get pods --namespace=kube-system -l k8s-app=coredns -o name); do kubectl logs --namespace=kube-system $p; done ``` Here is an example of a healthy CoreDNS log: