From ab1c0bb425a4310ac70d72c065e17f1e0bd7a3a0 Mon Sep 17 00:00:00 2001 From: Chris O'Haver Date: Tue, 30 Apr 2019 08:42:14 -0400 Subject: [PATCH] plugin/loop: Update troubleshooting step (#2804) * Update README.md --- plugin/loop/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/plugin/loop/README.md b/plugin/loop/README.md index c893ed050..df89caae4 100644 --- a/plugin/loop/README.md +++ b/plugin/loop/README.md @@ -80,7 +80,7 @@ requests to itself. There are many ways to work around this issue, some are listed here: -* Add the following to `kubelet`: `--resolv-conf `. Your "real" +* Add the following to your `kubelet` config yaml: `resolvConf: ` (or via command line flag `--resolv-conf` deprecated in 1.10). Your "real" `resolv.conf` is the one that contains the actual IPs of your upstream servers, and no local/loopback address. This flag tells `kubelet` to pass an alternate `resolv.conf` to Pods. For systems using `systemd-resolved`, `/run/systemd/resolve/resolv.conf` is typically the location of the "real" `resolv.conf`,