-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.21
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
CORENET Sprint 276
-
1
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
Clusters that have been previously upgraded from OpenShift 4.14 will still have the default-account-cluster-network-operator ClusterRoleBinding even though the network-operator now uses its own Service Account (SA). oc get clusterrolebinding default-account-cluster-network-operator NAME ROLE AGE default-account-cluster-network-operator ClusterRole/cluster-admin 4h8m oc get deployment network-operator -n openshift-network-operator -o yaml | yq '.spec.template.spec.serviceAccountName' cluster-network-operator
Version-Release number of selected component (if applicable):
OpenShift Container Platform 4.15+
How reproducible:
Easily
Steps to Reproduce:
1. Start with a OpenShift 4.14 cluster. 2. Upgrade to OpenShift 4.15 or higher.
Actual results:
The default-account-cluster-network-operator ClusterRoleBinding still exists in the cluster.
Expected results:
The default-account-cluster-network-operator ClusterRoleBinding no longer exists in the cluster.
Additional info: