From 4f675f30520898adfbd9d7db8f08e0903f6ba21b Mon Sep 17 00:00:00 2001 From: "Rostislav M. Georgiev" Date: Sat, 24 Nov 2018 18:05:36 +0200 Subject: [PATCH] kubeadm: Warn about overlapping networks (#11225) Signed-off-by: Rostislav M. Georgiev --- content/en/docs/setup/independent/create-cluster-kubeadm.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/content/en/docs/setup/independent/create-cluster-kubeadm.md b/content/en/docs/setup/independent/create-cluster-kubeadm.md index 1b40c1acca..8db68b4f83 100644 --- a/content/en/docs/setup/independent/create-cluster-kubeadm.md +++ b/content/en/docs/setup/independent/create-cluster-kubeadm.md @@ -245,6 +245,9 @@ support [Network Policy](/docs/concepts/services-networking/networkpolicies/). S Note that kubeadm sets up a more secure cluster by default and enforces use of [RBAC](/docs/reference/access-authn-authz/rbac/). 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. +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: ```bash