Hands-on Lab·Certified Kubernetes Security Specialist
Namespace Isolation for Multi-Tenancy
A namespace separates names and nothing else. This guide builds the six objects that turn one into a boundary, proves each of them from the outside and the inside, and finishes on the thing no combination of Kubernetes objects will separate.
Microservice Vulnerabilities Guide 22 of 40 Advanced
- 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 20 min
- Reviewed25 August 2026
Written against the versions above. Every object here is standard Kubernetes - no operator, no policy engine and nothing installed. This is the template a platform team applies to every new tenant.
| 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
-
A namespace is not a boundary until you make it one
-
The six objects that make one
-
Test the boundary from both directions
-
What a namespace still cannot separate