Command Palette

Search for a command to run...

Hectal
Phase 2Intermediate3 of 10 in Kubernetes

Configuration & Storage

Keep config and secrets out of your container images, organize a shared cluster cleanly, and give pods storage that actually survives their own disposable lifecycle.

A container image should be identical across dev, staging, and production — ConfigMaps and Secrets are how the actual configuration gets injected at runtime instead. Namespaces are how a shared cluster stays organized. And volumes solve the genuinely important problem this phase closes with: a pod's local filesystem disappears the moment it does, so anything that needs to survive has to live somewhere else entirely.

0/4 · 0%
4 topics ~56 min 10 code blocks & diagrams
Start with the first topic
1
2.1

ConfigMaps & Secrets

A ConfigMap holds non-sensitive configuration, a Secret holds sensitive values — both let you inject configuration into a pod at runtime without ever baking it into the container image itself.

14 min 2 code practice

2
2.2

Namespaces: Organizing a Shared Cluster

A Namespace is a virtual sub-division of a cluster — the standard way to separate teams, environments, or applications sharing the same physical cluster without their resources colliding or interfering.

14 min 2 code practice

3
2.3

Volumes, PersistentVolumes & PersistentVolumeClaims

A pod's own filesystem disappears the moment it's replaced — a Volume gives it storage that outlives the container, and a PersistentVolume/Claim pair is how that storage survives the pod itself being deleted and recreated.

14 min 1 diagram 2 code practice

4
2.4

StorageClasses & Dynamic Provisioning

A StorageClass lets Kubernetes automatically create a new PersistentVolume on demand, exactly matching what a PVC asks for — removing the need to manually pre-create storage before any application can use it.

14 min 1 diagram 2 code practice