Bug 1833125 - Resource Graph is Built Using Legacy Router CA ConfigMap
Summary: Resource Graph is Built Using Legacy Router CA ConfigMap
Keywords:
Status: CLOSED DUPLICATE of bug 1833128
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: kube-controller-manager
Version: 4.5
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.4.z
Assignee: Maciej Szulik
QA Contact: zhou ying
URL:
Whiteboard:
Depends On: 1830364 1833128
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-07 20:30 UTC by OpenShift BugZilla Robot
Modified: 2020-05-07 20:41 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-07 20:41:09 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description OpenShift BugZilla Robot 2020-05-07 20:30:38 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 Daneyon Hansen 2020-05-07 20:41:09 UTC 

*** This bug has been marked as a duplicate of bug 1833128 ***
Note You need to log in before you can comment on or make changes to this bug.