From 63420166a1d3b4b56225792b71d536d05010171e Mon Sep 17 00:00:00 2001 From: prameshj Date: Sun, 5 Dec 2021 17:28:32 -0800 Subject: [PATCH] Update docs to clarify the dns configmap format. (#29988) * Update docs to clarify the dns configmap format. * Update content/en/docs/tasks/administer-cluster/nodelocaldns.md Co-authored-by: Qiming Teng Co-authored-by: Qiming Teng --- content/en/docs/tasks/administer-cluster/nodelocaldns.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/content/en/docs/tasks/administer-cluster/nodelocaldns.md b/content/en/docs/tasks/administer-cluster/nodelocaldns.md index e2038a7223..4568182251 100644 --- a/content/en/docs/tasks/administer-cluster/nodelocaldns.md +++ b/content/en/docs/tasks/administer-cluster/nodelocaldns.md @@ -91,4 +91,13 @@ If you are using the sample manifest from the previous point, this will require Once enabled, node-local-dns Pods will run in the kube-system namespace on each of the cluster nodes. This Pod runs [CoreDNS](https://github.com/coredns/coredns) in cache mode, so all CoreDNS metrics exposed by the different plugins will be available on a per-node basis. You can disable this feature by removing the DaemonSet, using `kubectl delete -f ` . You should also revert any changes you made to the kubelet configuration. + +## StubDomains and Upstream server Configuration + +StubDomains and upstream servers specified in the `kube-dns` ConfigMap in the `kube-system` namespace +are automatically picked up by `node-local-dns` pods. The ConfigMap contents need to follow the format +shown in [the example](/docs/tasks/administer-cluster/dns-custom-nameservers/#example-1). +The `node-local-dns` ConfigMap can also be modified directly with the stubDomain configuration +in the Corefile format. Some cloud providers might not allow modifying `node-local-dns` ConfigMap directly. +In those cases, the `kube-dns` ConfigMap can be updated.