From da3fbcf3ed1a767901dd1e8fd8596a6f54953a98 Mon Sep 17 00:00:00 2001 From: Martin Hoefling Date: Wed, 24 Oct 2018 05:25:19 +0200 Subject: [PATCH] Fix incorrect naming of the flag (#10713) The flag is called --resolv-conf. --- content/en/docs/setup/independent/kubelet-integration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/setup/independent/kubelet-integration.md b/content/en/docs/setup/independent/kubelet-integration.md index 926d26e1a9..cd56d6c4b4 100644 --- a/content/en/docs/setup/independent/kubelet-integration.md +++ b/content/en/docs/setup/independent/kubelet-integration.md @@ -70,7 +70,7 @@ For more details on the ComponentConfig have a look at [this section](#configure Some hosts require specific kubelet configurations, due to differences in hardware, operating system, networking, or other host-specific parameters. The following list provides a few examples. -- The path to the DNS resolution file, as specified by the `--resolve-conf` kubelet +- The path to the DNS resolution file, as specified by the `--resolv-conf` kubelet configuration flag, may differ among operating systems, or depending on whether you are using `systemd-resolved`. If this path is wrong, DNS resolution will fail on the Node whose kubelet is configured incorrectly.