-
Bug
-
Resolution: Not a Bug
-
None
-
None
-
False
-
-
False
-
CLOSED
-
---
-
---
-
Medium
-
None
Description of problem:
-----------------------
Test run[1] that looks for 'pod security violation entries' in audit logs,against 4.11.1-20, found few audit violation.
This bug is to fix violation in 'mounter' container.
<snip>
'pod-security.kubernetes.io/audit-violations': 'would violate PodSecurity "restricted:latest": privileged (container "mounter" must not set securityContext.privileged=true), allowPrivilegeEscalation != false (container "mounter" must set securityContext.allowPrivilegeEscalation=false), unrestricted capabilities (container "mounter" must set securityContext.capabilities.drop=["ALL"]), restricted volume types (volume "host-root" uses restricted volume type "hostPath"), runAsNonRoot != true (pod or container "mounter" must set securityContext.runAsNonRoot=true), seccompProfile (pod or container "mounter" must set securityContext.seccompProfile.type to "RuntimeDefault" or "Localhost")'
</snip>
Version-Release number of selected component (if applicable):
-------------------------------------------------------------
4.11.1-20
How reproducible:
-----------------
Always
Expected results:
-----------------
No audit-violation to be found
- blocks
-
CNV-18561 [2089744] HCO should label its control plane namespace to admit pods at privileged security level
- Closed