Update bootkube.md

removed the requirement to edit kubelet manifest, as now kube-router gets node name from env variable
This commit is contained in:
Murali Reddy 2017-06-07 03:36:16 +05:30 committed by GitHub
parent d4f32978fb
commit 3524a2a0ae

View File

@ -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 <instance id>--no-source-dest-check aws ec2 modify-instance-attribute --instance-id <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 ## Cluster Startup
Finally, proceed by following the Bootkube documentation, which generally Finally, proceed by following the Bootkube documentation, which generally