From 4e0ee8b5c6529fbe61f389ce770a03497b98a528 Mon Sep 17 00:00:00 2001 From: Florian Breisch Date: Thu, 4 Oct 2018 04:43:16 +0200 Subject: [PATCH] Fix misspelled plugin configuration option (#10421) --- .../en/docs/tasks/administer-cluster/dns-custom-nameservers.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/tasks/administer-cluster/dns-custom-nameservers.md b/content/en/docs/tasks/administer-cluster/dns-custom-nameservers.md index 7067097b0b..4f019473c6 100644 --- a/content/en/docs/tasks/administer-cluster/dns-custom-nameservers.md +++ b/content/en/docs/tasks/administer-cluster/dns-custom-nameservers.md @@ -94,7 +94,7 @@ The Corefile configuration includes the following [plugins](https://coredns.io/p * [health](https://coredns.io/plugins/health/): Health of CoreDNS is reported to http://localhost:8080/health. * [kubernetes](https://coredns.io/plugins/kubernetes/): CoreDNS will reply to DNS queries based on IP of the services and pods of Kubernetes. You can find more details [here](https://coredns.io/plugins/kubernetes/). -> The `pods insecure` option is provided for backward compatibility with kube-dns. You can use the `pod verified` option, which returns an A record only if there exists a pod in same namespace with matching IP. The `pods disabled` option can be used if you don't use pod records. +> The `pods insecure` option is provided for backward compatibility with kube-dns. You can use the `pods verified` option, which returns an A record only if there exists a pod in same namespace with matching IP. The `pods disabled` option can be used if you don't use pod records. > `Upstream` is used for resolving services that point to external hosts (External Services).