Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1833120

Summary: kube-sceduler-operator targetconfig controller uses legacy router configmap
Product: OpenShift Container Platform Reporter: OpenShift BugZilla Robot <openshift-bugzilla-robot>
Component: kube-schedulerAssignee: Maciej Szulik <maszulik>
Status: CLOSED DUPLICATE QA Contact: RamaKasturi <knarra>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.5CC: aos-bugs, mfojtik
Target Milestone: ---   
Target Release: 4.4.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-05-11 10:12:48 UTC Type: ---
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: 1830406, 1833122    
Bug Blocks:    

Description OpenShift BugZilla Robot 2020-05-07 20:24:29 UTC 
This is a clone of Bug #1830406. This is the description of that bug:
Description of problem:
kube-sceduler-operator uses the legacy cm/router-ca -n openshift-config-managed to build cm/serviceaccount-ca -n openshift-kube-scheduler. As with [1], kube-sceduler-operator should use cm/default-ingress-cert -n openshift-config-managed.

Version-Release number of selected component (if applicable):
4.5

How reproducible:
N/A

Steps to Reproduce:
1.N/A

Actual results:
N/A

Expected results:
N/A

Additional info:
[1] https://github.com/openshift/cluster-kube-controller-manager-operator/pull/402
Comment 1 Maciej Szulik 2020-05-11 10:12:48 UTC 

*** This bug has been marked as a duplicate of bug 1833122 ***