Bug 1898159 - kcm operator shall pass --allocate-node-cidrs=false to kcm for ovn-kube and openshift-sdn cluster
Summary: kcm operator shall pass --allocate-node-cidrs=false to kcm for ovn-kube and o...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: kube-controller-manager
Version: 4.7
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.7.0
Assignee: Maciej Szulik
QA Contact: RamaKasturi
URL:
Whiteboard:
Depends On:
Blocks: 1896365 1897026 1898831
TreeView+ depends on / blocked
 
Reported: 2020-11-16 14:48 UTC by Peng Liu
Modified: 2021-02-24 15:34 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 1898831 (view as bug list)
Environment:
Last Closed: 2021-02-24 15:33:36 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-kube-controller-manager-operator pull 480 0 None closed Bug 1898159: do not set allocate-node-cidrs, which is handled by ovn and sdn 2021-01-15 19:06:39 UTC
Red Hat Product Errata RHSA-2020:5633 0 None None None 2021-02-24 15:34:06 UTC

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


Note You need to log in before you can comment on or make changes to this bug.