-
Bug
-
Resolution: Duplicate
-
Critical
-
None
-
4.22.0
-
None
-
None
-
False
-
-
None
-
Critical
-
None
-
None
-
None
-
Rejected
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
openshift-cluster-csi-drivers/<random pod name> pod should not use default service account. As part of OCPSTRAT-2401, core OpenShift components should not be using default service account, but rather their own bespoke service account.
Version-Release number of selected component (if applicable):
How reproducible:
https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-gcp-filestore-csi-driver-operator-release-4.22-periodics-periodic-e2e-gcp-filestore-csi/2008035934162915328 test showed default service account usage in openshift-cluster-csi-drivers/<random pod name> pod .
Steps to Reproduce:
Running periodic-ci-openshift-gcp-filestore-csi-driver-operator-release-4.22-periodics-periodic-e2e-gcp-filestore-csi test should show default service account usage for openshift-cluster-csi-drivers/<random pod name> pod in the default service account monitor tests.
Actual results:
openshift-cluster-csi-drivers/<random pod name> pod is using default service account.
Expected results:
openshift-cluster-csi-drivers/<random pod name> pod should be using its own bespoke service account.
Additional info:
- blocks
-
OCPSTRAT-2401 Ensure Default Service Accounts are not used by OpenShift Operators
-
- In Progress
-
- is duplicated by
-
-
- POST
-
