Docker & Kubernetes for Interviews
Images, Pods, Services and rollouts — the container round, drawn as replicas moving through a cluster.
Docker & Kubernetes for Interviews progress0 / 12
- Containers vs VMsA VM brings its own kernel. A container is a fenced-off process on yours.6m
- Images, Layers & Multi-Stage BuildsOrder the Dockerfile by how often each line changes, and ship only the output.7m
- Ports, Networks & VolumesPrivate names, one published port, and data that outlives the container.6m
- Docker Compose for Local DevOne file, one command, a whole app — as long as it fits on one Docker host.6m
- Pods, ReplicaSets & DeploymentsDeclare how many and which version; three controllers keep reality matching it.7m
- Scheduling & Rolling UpdatesWhere a Pod lands, and how v1 becomes v2 without a gap in service.7m
- Services & IngressA stable name in front of Pods that come and go, and one front door for HTTP.7m
- ConfigMaps, Secrets & EnvOne image everywhere; the settings and the passwords live beside it, not in it.6m
- Probes & Self-HealingThree questions the kubelet keeps asking: started? ready? still alive?6m
- Requests, Limits & HPAReserve what a Pod needs, cap what it takes, and scale out when it runs hot.7m
- Storage: PV, PVC & StatefulSetReplicas with names that stick and disks that follow them.7m
- Design a Deployment on KubernetesWalk the request path, then name the failure each piece is there for.8m
Quiz yourself: 3 questions from this module
1 / 3