docker
/
docs
mirror of https://github.com/docker/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Updated Kubernetes networking defaults

This commit is contained in:
ollypom 2019-06-24 17:17:05 +00:00
parent d02cc3d6ff
commit 1617eebc63
No known key found for this signature in database
GPG Key ID: 2E6D9F4EBCB6B160
1 changed files with 14 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
ee/ucp/admin/install/plan-installation.md
View File

@ -42,13 +42,24 @@ this.
## Avoid IP range conflicts
The `service-cluster-ip-range` Kubernetes API Server flag is currently set to `10.96.0.0/16` and cannot be changed.
Swarm uses a default address pool of `10.0.0.0/8` for its overlay networks. If this conflicts with your current network implementation, please use a custom IP address pool. To specify a custom IP address pool, use the `--default-address-pool` command line option during [Swarm initialization](../../../../engine/swarm/swarm-mode.md).
> **Note**: Currently, the UCP installation process does not support this flag. To deploy with a custom IP pool, Swarm must first be installed using this flag and UCP must be installed on top of it.
Kubernetes uses a default cluster IP pool for pods that is `192.168.0.0/16`. If it conflicts with your current networks, please use a custom IP pool by specifying `--pod-cidr` during UCP installation.
### Kubernetes IP Range Conflicts
There are 2 internal IP ranges used within Kubernetes that may overlap and
conflict with the underlying infrastructure:
- The Pod Network. Each Pod in Kubernetes is given an IP address from either
the Calico or Azure IPAM services. In a default installation Pods are given
IP addresses on the `192.168.0.0/16` range. This can be customised at install
time using the `--pod-cidr` flag.
- The Services Network. When a user exposes a Service in Kubernetes it is
accesible on a VIP, this VIP comes from a Cluster IP Range. By default on UCP
this range is `10.96.0.0/16`. From UCP 3.1.8 and onwards this value can be
changed at install time with the `--service-cluster-ip-range` flag.
## Avoid firewall conflicts