From cad2e5c006df725b26ea89835fd152bf806740d6 Mon Sep 17 00:00:00 2001 From: mohamed chiheb ben jemaa Date: Tue, 9 Jul 2019 11:58:01 +0100 Subject: [PATCH] fixing coredns label (#15340) --- .../docs/tasks/administer-cluster/dns-debugging-resolution.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) 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 8dc097b2d2..61fe3f80d2 100644 --- a/content/en/docs/tasks/administer-cluster/dns-debugging-resolution.md +++ b/content/en/docs/tasks/administer-cluster/dns-debugging-resolution.md @@ -95,7 +95,7 @@ Use the `kubectl get pods` command to verify that the DNS pod is running. For CoreDNS: ```shell -kubectl get pods --namespace=kube-system -l k8s-app=coredns +kubectl get pods --namespace=kube-system -l k8s-app=kube-dns NAME READY STATUS RESTARTS AGE ... coredns-7b96bf9f76-5hsxb 1/1 Running 0 1h @@ -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=coredns -o name); do kubectl logs --namespace=kube-system $p; done +for p in $(kubectl get pods --namespace=kube-system -l k8s-app=kube-dns -o name); do kubectl logs --namespace=kube-system $p; done ``` Here is an example of a healthy CoreDNS log: