Fixed #1

Make sure kubeletes use `/run/systemd/resolve/resolv.conf` and not `/etc/resolv.conf` to make sure that any dnsmasq / resolved installed on the workers does not interfere with the clusters DNS resolution Refs: kubernetes/kubeadm#273 https://blog.sophaskins.net/blog/misadventures-with-kube-dns/
asksven · Sep 12, 2018 · bbf4d0a · bbf4d0a
1 parent 4255bff
commit bbf4d0a
Show file tree

Hide file tree

Showing 4 changed files with 8 additions and 4 deletions.
diff --git a/config/worker-0-kubelet.service b/config/worker-0-kubelet.service
@@ -23,7 +23,8 @@ ExecStart=/usr/local/bin/kubelet \
   --runtime-request-timeout=10m \
   --tls-cert-file=/var/lib/kubelet/worker-0.pem \
   --tls-private-key-file=/var/lib/kubelet/worker-0-key.pem \
-  --v=2
+  --v=2 \
+  --resolv-conf=/run/systemd/resolve/resolv.conf
 Restart=on-failure
 RestartSec=5
 

diff --git a/config/worker-1-kubelet.service b/config/worker-1-kubelet.service
@@ -23,7 +23,8 @@ ExecStart=/usr/local/bin/kubelet \
   --runtime-request-timeout=10m \
   --tls-cert-file=/var/lib/kubelet/worker-1.pem \
   --tls-private-key-file=/var/lib/kubelet/worker-1-key.pem \
-  --v=2
+  --v=2 \
+  --resolv-conf=/run/systemd/resolve/resolv.conf
 Restart=on-failure
 RestartSec=5
 

diff --git a/config/worker-2-kubelet.service b/config/worker-2-kubelet.service
@@ -23,7 +23,8 @@ ExecStart=/usr/local/bin/kubelet \
   --runtime-request-timeout=10m \
   --tls-cert-file=/var/lib/kubelet/worker-2.pem \
   --tls-private-key-file=/var/lib/kubelet/worker-2-key.pem \
-  --v=2
+  --v=2 \
+  --resolv-conf=/run/systemd/resolve/resolv.conf
 Restart=on-failure
 RestartSec=5
 

diff --git a/scripts/generate-kubelet-service-file b/scripts/generate-kubelet-service-file
@@ -31,7 +31,8 @@ ExecStart=/usr/local/bin/kubelet \\
   --runtime-request-timeout=10m \\
   --tls-cert-file=/var/lib/kubelet/worker-${i}.pem \\
   --tls-private-key-file=/var/lib/kubelet/worker-${i}-key.pem \\
-  --v=2
+  --v=2 \\
+  --resolv-conf=/run/systemd/resolve/resolv.conf
 Restart=on-failure
 RestartSec=5