-
Bug
-
Resolution: Duplicate
-
Undefined
-
None
-
4.11
-
None
-
Moderate
-
None
-
False
-
Description of problem:
When doing an "oc debug node/worker0", a warning is shown about violating the PodSecurity.
$ oc debug node/pwk-2
Warning: would violate PodSecurity "restricted:latest": host namespaces (hostNetwork=true, hostPID=true), privileged (container "container-00" must not set securityContext.privileged=true), allowPrivilegeEscalation != false (container "container-00" must set securityContext.allowPrivilegeEscalation=false), unrestricted capabilities (container "container-00" must set securityContext.capabilities.drop=["ALL"]), restricted volume types (volume "host" uses restricted volume type "hostPath"), runAsNonRoot != true (pod or container "container-00" must set securityContext.runAsNonRoot=true), runAsUser=0 (container "container-00" must not set runAsUser=0), seccompProfile (pod or container "container-00" must set securityContext.seccompProfile.type to "RuntimeDefault" or "Localhost")
Starting pod/pwk-2-debug ...
Version-Release number of selected component (if applicable):
How reproducible:
always
Steps to Reproduce:
1.do "oc debug node/$NODE"
2.
3.
Actual results:
PodSecurity warning is displayed
Expected results:
no warning
Additional info:
- duplicates
-
OCPBUGS-852 oc debug requires a user to create a namespace with specific security labels
- Closed