From ddb6636f2ce862cdcfe178e9b5b906ffbdf67818 Mon Sep 17 00:00:00 2001 From: Jamie Hannaford Date: Thu, 22 Jun 2017 11:30:58 +0200 Subject: [PATCH] Document kubeadm KUBELET_DNS_ARGS issue --- docs/admin/kubeadm.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/docs/admin/kubeadm.md b/docs/admin/kubeadm.md index 2c1f33718c..74f697c384 100644 --- a/docs/admin/kubeadm.md +++ b/docs/admin/kubeadm.md @@ -156,6 +156,16 @@ names `..svc.cluster.local`. You can use the update the `/etc/systemd/system/kubelet.service.d/10-kubeadm.conf` file accordingly else DNS will not function correctly. +**Note**: This flag has an effect (it's needed for the kube-dns Deployment +manifest and the API Server's serving certificate) but not as you might expect, +since you will have to modify the arguments to the kubelets in the cluster for +it to work fully. Specifying DNS parameters using this flag only is not enough. +Rewriting the kubelet's CLI arguments is out of scope for kubeadm as it should +be agnostic to how you run the kubelet. However, making all kubelets in the +cluster pick up information dynamically via the API _is_ in scope and is a +[planned feature](https://github.com/kubernetes/kubeadm/issues/28) for upcoming +releases. + - `--skip-preflight-checks` By default, kubeadm runs a series of preflight checks to validate the system