Config for Kubernetess
Kubernetes configuration is how settings, credentials and resource limits are supplied to containers without rebuilding images. ConfigMaps hold non-sensitive settings, Secrets hold sensitive values, and resource requests, limits and probes tell the scheduler and kubelet how much capacity a container needs and whether it is healthy.
Stage: Configuration and Storage · Part of the Kubernetes roadmap · Last reviewed 19 November 2026
What to learn in Config
- Inject a ConfigMap into a container as environment variables and as a mounted file
- Create a Secret and explain that base64 encoding is not encryption
- Set CPU and memory requests and limits and describe what happens when they are exceeded
- Configure liveness, readiness and startup probes for a web service
- Describe the Quality of Service classes assigned to Pods
Config interview questions
What is the difference between a readiness probe and a liveness probe?
A failing readiness probe removes the Pod from Service endpoints but leaves it running, so it stops receiving traffic. A failing liveness probe makes the kubelet restart the container. Use readiness for temporary unavailability and liveness for deadlocks that only a restart fixes.
What is the difference between resource requests and limits?
A request is the amount the scheduler reserves when placing the Pod. A limit is the maximum the container may use. Exceeding a memory limit gets the container killed as OOMKilled, while exceeding a CPU limit only throttles it.
Where Config fits in the Kubernetes roadmap
Config belongs to the Configuration and Storage stage (advanced level), which takes about 22 hours. State and settings.
Other units in this stage
Back to the full Kubernetes roadmap