Difference between revisions of "Spec.securityContext"
Jump to navigation
Jump to search
| Line 19: | Line 19: | ||
== Related == | == Related == | ||
* [[Kubernetes changelog]]: [[AppArmor]] profiles can now be configured through fields on the <code>[[PodSecurityContext]]</code> and container <code>[[SecurityContext]]</code> | * [[Kubernetes changelog]]: [[AppArmor]] profiles can now be configured through fields on the <code>[[PodSecurityContext]]</code> and container <code>[[SecurityContext]]</code> | ||
| − | * [[Configure a Security Context for a Pod or Container]] | + | * [[Configure a Security Context for a Pod or Container]]: <code>[[kind: Pod]]</code> |
== See also == | == See also == | ||
Revision as of 09:14, 21 May 2024
securityContext:
spec: securityContext: runAsNonRoot: true
runAsNonRoot runAsUser runAsGroup
Errors
Related
- Kubernetes changelog: AppArmor profiles can now be configured through fields on the
PodSecurityContextand containerSecurityContext - Configure a Security Context for a Pod or Container:
kind: Pod
See also
spec.securityContext, spec.securityContext.runAsUser, spec.securityContext.fsGroup- 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:
