From 3524a2a0aec38ff3a35e7e3764653e893fa11f8e Mon Sep 17 00:00:00 2001 From: Murali Reddy Date: Wed, 7 Jun 2017 03:36:16 +0530 Subject: [PATCH] Update bootkube.md removed the requirement to edit kubelet manifest, as now kube-router gets node name from env variable --- Documentation/bootkube.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/Documentation/bootkube.md b/Documentation/bootkube.md index 9c98bd65..76337c86 100644 --- a/Documentation/bootkube.md +++ b/Documentation/bootkube.md @@ -62,8 +62,6 @@ Since kube-router uses node routing rules to directly route pod-to-pod traffic t aws ec2 modify-instance-attribute --instance-id --no-source-dest-check ``` -Bootkube deploys kubelet with `--hostname-override=${COREOS_PRIVATE_IPV4}` in the manifest which means nodes will register with IP address instead of node hostname to Kubernetes API server. Which will cause problem for both Kube-proxy (unless you use `--hostname-override `with kube-proxy as well) and Kube-router. Kube-router does not implement `--hostname-override` yet. So remove `--hostname-override` flag from both kubelet.master and kubelet.worker manifests. - ## Cluster Startup Finally, proceed by following the Bootkube documentation, which generally