securityContext
Configure the Security Context for the Pod.
object
Properties
Section titled “Properties”| Property | Type | Required | Default | Description |
|---|---|---|---|---|
fsGroup | integer | No | - | A special supplemental group that applies to all containe… |
fsGroupChangePolicy | string | No | - | fsGroupChangePolicy defines behavior of changing ownershi… |
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 all containers. If u… |
seccompProfile | object | No | - | The seccomp options to use by the containers in this pod… |
supplementalGroups | array | No | - | A list of groups applied to the first process run in each… |
supplementalGroupsPolicy | string | No | - | Defines how supplemental groups of the the first process … |
sysctls | array | No | - | Sysctls hold a list of namespaced sysctls used for the po… |
Property Details
Section titled “Property Details”fsGroup
Section titled “fsGroup”A special supplemental group that applies to all containers in a pod. Some volume types allow the Kubelet to change the ownership of that volume to be owned by the pod:
- The owning GID will be the FSGroup 2. The setgid bit is set (new files created in the volume will be owned by FSGroup) 3. The permission bits are OR’d with rw-rw----
If unset, the Kubelet will not modify the ownership and permissions of any volume. Note that this field cannot be set when spec.os.name is windows.
fsGroupChangePolicy
Section titled “fsGroupChangePolicy”fsGroupChangePolicy defines behavior of changing ownership and permission of the volume before being exposed inside Pod. This field will only apply to volume types which support fsGroup based ownership(and permissions). It will have no effect on ephemeral volume types such as: secret, configmaps and emptydir. Valid values are “OnRootMismatch” and “Always”. If not specified, “Always” is used. 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 SecurityContext. If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence for that container. 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 SecurityContext. 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 SecurityContext. If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence for that container. Note that this field cannot be set when spec.os.name is windows.
supplementalGroups
Section titled “supplementalGroups”A list of groups applied to the first process run in each container, in addition to the container’s primary GID, the fsGroup (if specified), and group memberships defined in the container image for the uid of the container process. If unspecified, no additional groups are added to any container. Note that group memberships defined in the container image for the uid of the container process are still effective, even if they are not included in this list. Note that this field cannot be set when spec.os.name is windows.
supplementalGroupsPolicy
Section titled “supplementalGroupsPolicy”Defines how supplemental groups of the the first process in each container are calculated. Valid values are “Merge” and “Strict”. If not specified, “Merge” is used. Note that this field cannot be set when spec.os.name is windows.
Allowed values: Merge, Strict
sysctls
Section titled “sysctls”Sysctls hold a list of namespaced sysctls used for the pod. Pods with unsupported sysctls (by the container runtime) might fail to launch. Note that this field cannot be set when spec.os.name is windows.