Difference between revisions of "Spec.securityContext"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
{{lc}} | {{lc}} | ||
| − | |||
| − | |||
| − | |||
spec: | spec: | ||
| Line 9: | Line 6: | ||
[[runAsGroup]]: 3000 | [[runAsGroup]]: 3000 | ||
fsGroup: 2000 | fsGroup: 2000 | ||
| + | |||
| + | [[spec:]] | ||
| + | securityContext: | ||
| + | [[runAsNonRoot]]: true | ||
| + | |||
| + | |||
== Examples == | == Examples == | ||
Revision as of 18:26, 27 October 2024
spec:
securityContext:
runAsUser: 1000
runAsGroup: 3000
fsGroup: 2000
spec: securityContext: runAsNonRoot: true
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
PodSecurityContextand containerSecurityContext - Configure a Security Context for a Pod or Container:
kind: Pod
See also
containerSecurityContext, spec.securityContext, spec.securityContext.runAsUser, spec.securityContext.fsGroupkind: 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:
