Kubernetes
A control loop that keeps your containers in the state you declared.
clustersnodespodsdeploymentsservicesingressConfigMapsSecretsautoscalinghealth checksrolling updatesoperatorsservice mesh
Lessons
- 12.1Kubernetes explainedYou tell Kubernetes what should be running. It keeps checking, and fixes anything that drifts. Here's how, and when it's worth it. 30 min Kubernetes simulator
- 12.2Pods, Deployments and Services in depth"It deployed but nothing works" usually means the pieces can't find each other. Here's how they connect, through simple name tags. 30 min Kubernetes simulator
- 12.3Config and secretsBuild one image, hand it different settings in each environment, and learn why a Kubernetes "Secret" isn't as secret as its name. 30 min
- 12.4Health checks and rolloutsKubernetes asks your app three questions to decide whether to wait, hide it, or restart it. Get them right and deploys become boring. 30 min Kubernetes simulator Deployment strategies
- 12.5When not to use KubernetesKubernetes is powerful and expensive to run. Here's a simple way to decide whether you need it, or something much lighter. 30 min Monolith or microservices?
On the job: try it on your own project
If your team runs Kubernetes, ask Claude Code to read the manifests and explain each deployment's replicas, resource limits, health checks and secrets. If it does not, ask Claude Code to estimate what moving to Kubernetes would cost in effort. Either way, write a one-page note: the biggest risk in your current setup, or why you should not adopt Kubernetes yet.
Can you do this now?
0/4. Anything you can't tick yet: reopen that lesson's practice ladder.