ced4568andClaude Sonnet 5
682ef2de47
Adds all 8 ROOT 04 modules (why containers exist, images & containers, Docker CLI, container networking, container storage, Dockerfile & image build, Docker Compose, containers → Kubernetes) — 43 activities, using the nested Docker Engine Phase 6D built and tested. Modules 1, 2, and 8 are conceptual (no lab by design) — the honest bridge module (M8) explicitly names what Kubernetes adds beyond what this course already taught, without re-teaching Kubernetes itself. Adds 5 new hands-on Docker scenarios plus 2 MCQs, all against the real nested Docker Engine: docker-cli-basics (run/exec/inspect a real container), docker-container-networking (a genuine "works internally, unreachable from host" port-publishing failure, diagnosed and fixed by recreating the container with the correct `-p` flag), docker-container-storage (a real destroy/recreate cycle proving named-volume persistence, not just described), docker-build-image (a real Dockerfile, a real build, a real custom image run), and docker-compose-multiservice (a real two-service Compose application with a real published port). All tested end-to-end via the real scenario-validation API, including negative tests. Wires rootnode-containers-assessment (2 required + 4 random-draw scenarios) using the existing Phase 3B assessment engine. This completes the entire ROOT_ Foundations sequence (ROOT 01-04) — see docs/PHASE6E_ROOT_FOUNDATIONS_COMPLETION.md. Co-Authored-By: Claude Sonnet 5 <[email protected]>
41 lines
1.4 KiB
Markdown
41 lines
1.4 KiB
Markdown
# Knowledge Check: Containers → Kubernetes
|
|
|
|
---
|
|
|
|
**1. Does Kubernetes replace Docker/containers?**
|
|
|
|
*Answer:* No — Kubernetes orchestrates containers across many machines; it runs on top of the
|
|
same container concepts this course taught, not instead of them.
|
|
|
|
---
|
|
|
|
**2. Name one thing Kubernetes adds that a single-machine `docker run`/Compose setup
|
|
fundamentally can't do.**
|
|
|
|
*Answer:* Any reasonable answer from: scheduling across multiple machines, automatic
|
|
reconciliation to a desired state after a failure, service discovery across many changing
|
|
instances, automated health-based replacement, demand-based scaling, or coordinated rollout
|
|
across a fleet.
|
|
|
|
---
|
|
|
|
**3. What does "desired state" mean, in the sense this lesson introduced it?**
|
|
|
|
*Answer:* You declare what SHOULD be running; the orchestrator continuously works to make actual
|
|
reality match that declaration, including automatically after a failure — rather than a person
|
|
having to manually notice and fix drift.
|
|
|
|
---
|
|
|
|
**4. Why doesn't this course teach Kubernetes directly, ending here instead?**
|
|
|
|
*Answer:* This course's job was building the container/Linux/Git foundation Kubernetes assumes
|
|
— ROOT 05 builds on exactly this foundation to teach Kubernetes itself.
|
|
|
|
## Instructor Notes
|
|
|
|
**Facilitation:** Question 2 is worth collecting several different answers from the group — the
|
|
variety itself is evidence the "why Kubernetes" question actually landed.
|
|
|
|
**Approximate timing:** 5 minutes.
|