Bug 1833130

Summary: Resource Graph is Built Using Legacy Router CA ConfigMap
Product: OpenShift Container Platform Reporter: OpenShift BugZilla Robot <openshift-bugzilla-robot>
Component: kube-controller-managerAssignee: Maciej Szulik <maszulik>
Status: CLOSED WONTFIX QA Contact: zhou ying <yinzhou>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.5CC: aos-bugs, mfojtik
Target Milestone: ---   
Target Release: 4.3.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:09:52 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: 1830364    
Bug Blocks:    

Description OpenShift BugZilla Robot 2020-05-07 20:34:21 UTC 
This is a clone of Bug #1830364. This is the description of that bug:
Description of problem:
kube-controller-manager uses the legacy cm/router-ca -n openshift-config-managed to build its resource graph. However, the targetconfig controller uses the new cm/default-ingress-cert -n openshift-config-managed resource to build cm/serviceaccount-ca -n openshift-kube-controller-manager.

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

How reproducible:
Always

Steps to Reproduce:
1. N/A

Actual results:
N/A

Expected results:
N/A

Additional info:
[1] updated the targetconfig controller but did not update the resource graph.


[1] https://github.com/openshift/cluster-kube-controller-manager-operator/pull/402
Comment 1 Maciej Szulik 2020-05-11 10:09:52 UTC 
This fix is not needed in 4.3.