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 <tengqm@outlook.com> Co-authored-by: Qiming Teng <tengqm@outlook.com>pull/30751/head
parent
307252f513
commit
63420166a1
|
@ -92,3 +92,12 @@ Once enabled, node-local-dns Pods will run in the kube-system namespace on each
|
|||
|
||||
You can disable this feature by removing the DaemonSet, using `kubectl delete -f <manifest>` . 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.
|
||||
|
||||
|
|
Loading…
Reference in New Issue