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
Compared payload: 4.5.0-0.nightly-2020-05-06-003431 with payload: 4.4.0-0.nightly-2020-05-08-004736, the issue has fixed: oc exec po/kube-controller-manager-operator-xxx cluster-kube-controller-manager-operator resource-graph |dot -Tpng >output4.png
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, 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/RHBA-2020:2409