-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.20
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
Proposed
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
When running HCP on management clusters with no securityContextConstraints, hypershift ensures each HC namespace has its own securityContext UID.
This should be honour by operands, e.g. passing and env variable. These are currently not honouring the intended uid.
azure-disk-csi-driver-controller
azure-disk-csi-driver-operator
azure-file-csi-driver-controller
azure-file-csi-driver-operator
- is cloned by
-
OCPBUGS-60638 network operands should honour securityContext UID
-
- New
-
- links to
(1 links to)