Difference between revisions of "Spec.securityContext"
Jump to navigation
Jump to search
Line 23: | Line 23: | ||
== See also == | == See also == | ||
* {{SecurityContext}} | * {{SecurityContext}} | ||
+ | * {{kind: Pod}} | ||
* {{K8s security}} | * {{K8s security}} | ||
[[Category:K8s]] | [[Category:K8s]] |
Revision as of 18:22, 27 October 2024
spec: securityContext: runAsNonRoot: true
spec: securityContext: runAsUser: 1000 runAsGroup: 3000 fsGroup: 2000
Contents
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
Related
- Kubernetes changelog: AppArmor profiles can now be configured through fields on the
PodSecurityContext
and containerSecurityContext
- Configure a Security Context for a Pod or Container:
kind: Pod
See also
spec.securityContext, spec.securityContext.runAsUser, spec.securityContext.fsGroup
kind: Pod: spec.containers, spec.initContainers, spec.volumes, spec.securityContext
- 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: