Hands-on Lab·Certified Kubernetes Security Specialist
A securityContext That Passes the Restricted Standard
The previous guide ended with a refusal listing four fields. This one turns that list into a Pod that is admitted, then checks each control from inside the running container - and finishes with the field restricted never asks for and you should set anyway.
Microservice Vulnerabilities Guide 19 of 40 Intermediate
- Kubernetesapiserver v1.36.4, kubelet v1.36.3
- Runtimecontainerd 2.2.6
- CNICilium 1.18.1 - tunnel/VXLAN, with Hubble relay and UI
- Host OSUbuntu 26.04 LTS, kernel 7.0.0-29
- Built withkubeadm v1.36.3 - podSubnet 10.244.0.0/16, serviceSubnet 10.96.0.0/12
- TimeAbout 18 min
- Reviewed25 August 2026
Written against the versions above. The four fields are `runAsNonRoot`, `seccompProfile`, `allowPrivilegeEscalation` and `capabilities.drop` - two at Pod level and two at container level.
| Server Name | IP Address | OS | Roles | CPU | RAM | HDD |
|---|---|---|---|---|---|---|
| CKA6001 | 192.168.0.46 | Ubuntu 26.04 LTS | Control Plane Node (tainted NoSchedule) | 2 Core | 4 GB | 50 GB |
| CKA6001-NODE01 | 192.168.0.47 | Ubuntu 26.04 LTS | Worker Node | 2 Core | 4 GB | 50 GB |
| CKA6001-NODE02 | 192.168.0.48 | Ubuntu 26.04 LTS | Worker Node | 2 Core | 4 GB | 50 GB |
Before you start
-
The Pod that will not be admitted
-
Add them, and be admitted
-
Prove each control from inside
-
The field restricted does not require