Concepts·Certified Kubernetes Administrator
Pods: The Basic Deployment Unit
Kubernetes does not run containers, it runs Pods. Write one as YAML, see what the API server fills in that you did not, put two containers in one Pod and prove they share an address and a volume, then watch what happens when you delete it.
Foundations Guide 4 of 103 Beginner
- Kubernetes1.36.4
- Cluster4 nodes
- Runtimecontainerd 2.2.6
- CNICalico v3.32.1
- TimeAbout 30 min
- Reviewed21 August 2026
Written against the versions above. UIDs, resourceVersions, timestamps and pod addresses are generated per run. The manifests are the part to copy.
| Server Name | IP Address | OS | Roles | CPU | RAM | HDD |
|---|---|---|---|---|---|---|
| CKA1001 | 192.168.0.175 | Ubuntu 26.04 LTS | Control Plane Node | 2 Core | 4 GB | 50 GB |
| CKA1001-NODE01 | 192.168.0.176 | Ubuntu 26.04 LTS | Worker Node | 2 Core | 4 GB | 50 GB |
| CKA1001-NODE02 | 192.168.0.177 | Ubuntu 26.04 LTS | Worker Node | 2 Core | 4 GB | 50 GB |
| CKA1001-NODE03 | 192.168.0.178 | Ubuntu 26.04 LTS | Worker Node | 2 Core | 4 GB | 50 GB |
Before you start
- A working cluster and
kubectlconfigured against it. - Any container experience helps, but is not required. If you know
docker run, the interesting part is what Kubernetes adds around it. - A scratch namespace if you are on a shared cluster. Everything here runs in
defaultand is deleted at the end.
-
The smallest thing you can run
-
See what the API server added
-
Write the manifest yourself
-
Labels are the addressing system
-
Two containers, one Pod
-
Prove they share the volume, and that readOnly means it
-
One address for the whole Pod
-
A bare Pod does not come back
-
Clean up