securityContext
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.
object
Properties
Section titled “Properties”| Property | Type | Required | Default | Description |
|---|---|---|---|---|
allowPrivilegeEscalation | boolean | No | - | AllowPrivilegeEscalation controls whether a process can g… |
capabilities | object | No | - | The capabilities to add/drop when running containers. Def… |
privileged | boolean | No | - | Run container in privileged mode. Processes in privileged… |
procMount | string | No | - | procMount denotes the type of proc mount to use for the c… |
readOnlyRootFilesystem | boolean | No | - | Whether this container has a read-only root filesystem. D… |
runAsGroup | integer | No | - | The GID to run the entrypoint of the container process. U… |
runAsNonRoot | boolean | No | - | Indicates that the container must run as a non-root user… |
runAsUser | integer | No | - | The UID to run the entrypoint of the container process. D… |
seLinuxOptions | object | No | - | The SELinux context to be applied to the container. If un… |
seccompProfile | object | No | - | The seccomp options to use by this container. If seccomp … |
Property Details
Section titled “Property Details”allowPrivilegeEscalation
Section titled “allowPrivilegeEscalation”AllowPrivilegeEscalation 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.
privileged
Section titled “privileged”Run 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.
procMount
Section titled “procMount”procMount denotes the type of proc mount to use for the containers. The default is DefaultProcMount which uses the container runtime defaults for readonly paths and masked paths. This requires the ProcMountType feature flag to be enabled. Note that this field cannot be set when spec.os.name is windows.
readOnlyRootFilesystem
Section titled “readOnlyRootFilesystem”Whether this container has a read-only root filesystem. Default is false. Note that this field cannot be set when spec.os.name is windows.
runAsGroup
Section titled “runAsGroup”The 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.
runAsNonRoot
Section titled “runAsNonRoot”Indicates 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.
runAsUser
Section titled “runAsUser”The 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.