spec.securityContext

spec.securityContext
spec.containers.securityContext
             allowPrivilegeEscalation
             readOnlyRootFilesystem

spec:
  securityContext:
    runAsUser: 1000
    runAsGroup: 3000
    fsGroup: 2000

spec:
 securityContext:
   runAsNonRoot: true

Examples

 apiVersion: v1
kind: Pod
metadata:
  name: security-context-demo
spec:
  securityContext:
    runAsUser: 1000
    runAsGroup: 3000
    fsGroup: 2000
  volumes:
  - name: sec-ctx-vol
    emptyDir: {}
  containers:
  - name: sec-ctx-demo
    image: busybox:1.28
    command: [ "sh", "-c", "sleep 1h" ]
    volumeMounts:
    - name: sec-ctx-vol
      mountPath: /data/demo
    securityContext:
      allowPrivilegeEscalation: false

Errors

• Error: container's runAsUser breaks non-root policy

Related

• Kubernetes changelog: AppArmor profiles can now be configured through fields on the PodSecurityContext and container SecurityContext
• Configure a Security Context for a Pod or Container: kind: Pod
• USER

See also

• securityContext, containerSecurityContext, spec.containers.securityContext, spec.securityContext, spec.securityContext.runAsUser, spec.securityContext.fsGroup, readOnlyRootFilesystem
• kind: Pod: spec.containers, spec.initContainers, spec.volumes, spec.securityContext, spec.imagePullSecrets
• Kubernetes security, OPA, EKS security, PSA, PSS, CKS, SecurityContext, containerSecurityContext, Trivy, KubeBench, Kubernetes Admission Controllers admissionregistration.k8s.io, Hardeneks, Gatekeeper (Kubernetes), kubernetes.io/enforce-mountable-secrets, Auditing, security context, readOnlyRootFilesystem, allowPrivilegeEscalation, kube-bench