Simple definition
A Kubernetes securityContext defines privilege and access-control settings for a Pod or container.
Purpose and use
It helps limit workload capabilities and align execution with the environment’s security requirements.
How does it work?
Relevant fields can specify users, groups, Linux capabilities, privileged mode and selected system-security settings. Availability depends on the platform.
Key points
- Example: a container is designed to run without the root user and without unnecessary Linux capabilities.
- Verify the effective settings, image requirements and permissions on mounted volumes.
Points to watch
A securityContext does not replace network policies or RBAC. Pod and container settings do not all have the same scope or override behavior.
In short
The securityContext describes execution security conditions; admission policy can enforce selected limits.