medium10 pts · first answer countsdevsecopskubernetes

Pod rejected by the restricted profile

A namespace is labelled pod-security.kubernetes.io/enforce=restricted. A Pod that runs as root with default settings is rejected. Which settings are needed to pass?

A.A higher PriorityClass and a memory limit on every containerB.An image pulled by digest instead of by tagC.runAsNonRoot, no privilege escalation, drop ALL caps, RuntimeDefault seccompD.A ServiceAccount with cluster-admin rights

Discussion 0

Join free to post in the discussion.

Pod rejected by the restricted profile

Discussion 0

Related questions