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 , kube-sceduler-operator should use cm/default-ingress-cert -n openshift-config-managed.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Verified the bug with the payload below and i did not find any references to router-ca in audit logs for 4.5 cluster.
[ramakasturinarra@dhcp35-60 cucushift]$ oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.5.0-0.nightly-2020-05-13-092431 True False 21h Cluster version is 4.5.0-0.nightly-2020-05-13-092431
Below are the steps followed to verify the bug:
1) Install 4.5 cluster with latest build
2) oc project "openshift-kube-apiserver"
3) oc cp <kube-apiserver-pod-name>:/var/log/kube-api-server/audit.log /tmp/oc45.log
4) cat /tmp/oc45.log | grep "router-ca"
[ramakasturinarra@dhcp35-60 cucushift]$ cat /tmp/oc45.log | grep "router-ca"
[ramakasturinarra@dhcp35-60 cucushift]$ cat /tmp/oc45.log | grep "default-ingress-cert" | wc -l
Based on that moving the bug to verified state.
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.