whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

pod-network to be done only on master node (#15505)

Browse Source 
* pod-network to be done only on master node

added a note saying that Install a pod-network add on need to be done only on the master node

* updated where to run pod-network doc
This commit is contained in:
Alex Punnen
2019-07-25 13:05:53 +05:30
committed by Kubernetes Prow Robot
parent bb9ee3db9b
commit 14c348819f
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm.md
+1 -1
View File
@@ -270,7 +270,7 @@ Make sure that your network manifest supports RBAC.
Also, beware, that your Pod network must not overlap with any of the host networks as this can cause issues. Also, beware, that your Pod network must not overlap with any of the host networks as this can cause issues.
If you find a collision between your network plugin’s preferred Pod network and some of your host networks, you should think of a suitable CIDR replacement and use that during `kubeadm init` with `--pod-network-cidr` and as a replacement in your network plugin’s YAML. If you find a collision between your network plugin’s preferred Pod network and some of your host networks, you should think of a suitable CIDR replacement and use that during `kubeadm init` with `--pod-network-cidr` and as a replacement in your network plugin’s YAML.
You can install a pod network add-on with the following command: You can install a pod network add-on with the following command on the control-plane node or a node that has the kubeconfig credentials:
```bash ```bash
kubectl apply -f <add-on.yaml> kubectl apply -f <add-on.yaml>