Difference between revisions of "Spec.securityContext"
Jump to navigation
Jump to search
| Line 2: | Line 2: | ||
[[securityContext:]] | [[securityContext:]] | ||
| − | + | ||
[[runAsNonRoot]] | [[runAsNonRoot]] | ||
[[runAsUser]] | [[runAsUser]] | ||
[[runAsGroup]] | [[runAsGroup]] | ||
| + | |||
| + | == Errors == | ||
| + | * [[Error: container's runAsUser breaks non-root policy]] | ||
== Related == | == Related == | ||
Revision as of 07:29, 21 May 2024
securityContext:
runAsNonRoot runAsUser runAsGroup
Errors
Related
- Kubernetes changelog: AppArmor profiles can now be configured through fields on the
PodSecurityContextand containerSecurityContext
See also
containerSecurityContext, spec.securityContext, spec.securityContext.runAsUser, spec.securityContext.fsGroup- CKA: v1.28: API, Namespace, Pods, secrets, Services, deployments, nodes, Volumes, Ingress, CKS
- Kubernetes security, OPA, EKS security, PSA, PSS, CKS,
SecurityContext, Trivy, KubeBench, Kubernetes Admission Controllersadmissionregistration.k8s.io, Hardeneks, Gatekeeper (Kubernetes),kubernetes.io/enforce-mountable-secrets, Auditing
Advertising:
