V1SecurityContext

May 5, 2026 ยท View on GitHub

SecurityContext holds security configuration that will be applied to a container. Some fields are present in both SecurityContext and PodSecurityContext. When both are set, the values in SecurityContext take precedence.

Properties

NameTypeDescriptionNotes
allow_privilege_escalationboolAllowPrivilegeEscalation controls whether a process can gain more privileges than its parent process. This bool directly controls if the no_new_privs flag will be set on the container process. AllowPrivilegeEscalation is true always when the container is: 1) run as Privileged 2) has CAP_SYS_ADMIN Note that this field cannot be set when spec.os.name is windows.[optional]
app_armor_profileV1AppArmorProfile[optional]
capabilitiesV1Capabilities[optional]
privilegedboolRun container in privileged mode. Processes in privileged containers are essentially equivalent to root on the host. Defaults to false. Note that this field cannot be set when spec.os.name is windows.[optional]
proc_mountstrprocMount denotes the type of proc mount to use for the containers. The default value is Default which uses the container runtime defaults for readonly paths and masked paths. Note that this field cannot be set when spec.os.name is windows.[optional]
read_only_root_filesystemboolWhether this container has a read-only root filesystem. Default is false. Note that this field cannot be set when spec.os.name is windows.[optional]
run_as_groupintThe GID to run the entrypoint of the container process. Uses runtime default if unset. May also be set in PodSecurityContext. If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence. Note that this field cannot be set when spec.os.name is windows.[optional]
run_as_non_rootboolIndicates that the container must run as a non-root user. If true, the Kubelet will validate the image at runtime to ensure that it does not run as UID 0 (root) and fail to start the container if it does. If unset or false, no such validation will be performed. May also be set in PodSecurityContext. If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence.[optional]
run_as_userintThe UID to run the entrypoint of the container process. Defaults to user specified in image metadata if unspecified. May also be set in PodSecurityContext. If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence. Note that this field cannot be set when spec.os.name is windows.[optional]
se_linux_optionsV1SELinuxOptions[optional]
seccomp_profileV1SeccompProfile[optional]
windows_optionsV1WindowsSecurityContextOptions[optional]

[Back to Model list] [Back to API list] [Back to README]