mirror of
https://github.com/k3s-io/kubernetes.git
synced 2025-11-12 21:40:29 +00:00
7634cc01c5
kube-controller-manager. If a service CIDR that overlaps with the cluster CIDR is specified to kube-controller-manager then kube-controller- manager will incorrectly allocate node CIDRs that overlap with the service CIDR. The fix ensure that kubeadm maps the --service-cidr to --service-cluster-ip-range for use by kube-controller-manager. As per docs, --allocate-node-cidrs must be true for --service-cluster-ip-range to be considered. It does not make sense for --cluster-cidr to be unspecified but for --service-cluster-ip-range and --allocate-node-cidrs to be set, since the purpose of these options is to have the controller-manager do the per node CIDR allocation. Also note that --service-cluster-ip-range is passed to the api-server, so the presence of *just* --service-cluster-ip-range should not imply that --allocate-node-cidrs should be true. Resolves: kubernetes/kubeadm/issues/1591