aboutsummaryrefslogtreecommitdiff
path: root/plugin/loop
diff options
context:
space:
mode:
Diffstat (limited to 'plugin/loop')
-rw-r--r--plugin/loop/README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/plugin/loop/README.md b/plugin/loop/README.md
index df89caae4..eb3a1ee90 100644
--- a/plugin/loop/README.md
+++ b/plugin/loop/README.md
@@ -87,5 +87,5 @@ There are many ways to work around this issue, some are listed here:
although this can be different depending on your distribution.
* Disable the local DNS cache on host nodes, and restore `/etc/resolv.conf` to the original.
* A quick and dirty fix is to edit your Corefile, replacing `forward . /etc/resolv.conf` with
-the ip address of your upstream DNS, for example `forward . 8.8.8.8`. But this only fixes the issue for CoreDNS,
+the IP address of your upstream DNS, for example `forward . 8.8.8.8`. But this only fixes the issue for CoreDNS,
kubelet will continue to forward the invalid `resolv.conf` to all `default` dnsPolicy Pods, leaving them unable to resolve DNS.