You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 13, 2022. It is now read-only.
Our Kubernetes cluster resides on our corporate LAN and are thus bound by our existing deployed networks. The default pod and service network cidr's overlap with those of existing networks and create numerous issues due to colliding IPs.
We need the ability to configure designated networks for Kubernetes services and pods at deploy time to avoid network collisions. At present kubeadm exposes --pod-network-cidr and --service-cidr on it's init command for this purpose.
The text was updated successfully, but these errors were encountered:
Our Kubernetes cluster resides on our corporate LAN and are thus bound by our existing deployed networks. The default pod and service network cidr's overlap with those of existing networks and create numerous issues due to colliding IPs.
We need the ability to configure designated networks for Kubernetes services and pods at deploy time to avoid network collisions. At present kubeadm exposes --pod-network-cidr and --service-cidr on it's init command for this purpose.
The text was updated successfully, but these errors were encountered: