Bug 1898159

Summary:	kcm operator shall pass --allocate-node-cidrs=false to kcm for ovn-kube and openshift-sdn cluster
Product:	OpenShift Container Platform	Reporter:	Peng Liu <pliu>
Component:	kube-controller-manager	Assignee:	Maciej Szulik <maszulik>
Status:	CLOSED ERRATA	QA Contact:	RamaKasturi <knarra>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.7	CC:	aos-bugs, dosmith, knarra, mfojtik, yinzhou
Target Milestone:	---
Target Release:	4.7.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:
Clones:	1898831 (view as bug list)		Environment:
Last Closed:	2021-02-24 15:33:36 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1896365, 1897026, 1898831

Description Peng Liu 2020-11-16 14:48:17 UTC

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:

Comment 5 errata-xmlrpc 2021-02-24 15:33:36 UTC

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