Hide Forgot
Description of problem: By default, the kcm-operator pass default configuration to kcm with 'allocate-node-cidrs=true'. With such configuration, the kcm will allocate `podCIDR` in node.spec. However, openshift-sdn and ovn-kubernetes both do their own CIDR allocation. So the `podCIDR` is not utilized by either of them. Additionally, as we set 'allocate-node-cidrs=false', we shall not pass 'cluster-cidr' and 'service-cluster-ip-range' for kcm either. Version-Release number of selected component (if applicable): How reproducible: Install a cluster with openshift-sdn or ovn-kubernetes as the cluster network provider. Steps to Reproduce: 1. 2. 3. Actual results: $ oc logs -n openshift-kube-controller-manager kube-controller-manager-ip-10-0-160-243.us-west-2.compute.internal ... I1116 14:42:55.218650 1 flags.go:59] FLAG: --allocate-node-cidrs="true" ... Expected results: I1116 14:42:55.218650 1 flags.go:59] FLAG: --allocate-node-cidrs="false" Additional info:
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:5633