6 — Containers, Docker & Kubernetes

A C O N C E P T U A L A N D R E F E R E N C E C O U R S E Containers and Orchestration: Docker to Kubernetes Why containers exist, what Docker actually does, and when an orchestrator earns its keep. Standalone deck. Every term is defined on first use. Depth over hands-on labs. By Md Ahbab Hamid Khan

Agenda Seven sections, roughly one hundred slides ■ 01 What a container actually is: namespaces, cgroups, union filesystems ■ 02 Docker images, layers and the Dockerfile instruction by instruction ■ 03 Production Dockerfiles for six real application stacks ■ 04 Storage, networking and full multi service Docker Compose stacks ■ 05 Registries, tagging strategy and vulnerability scanning ■ 06 Kubernetes from first principles, then 07 scaling, GitOps and honest decisions Key takeaways appear at the end of every section. Glossary and further reading close the deck. Containers and Orchestration: Docker to Kubernetes 2

Assumed prerequisites What this deck takes for granted You program Fluent in at least one language. Comfortable with functions, classes and modules. Async and concurrency You know what a blocking call is and why worker processes exist. HTTP Methods, status codes, headers, ports, reverse proxies and TLS termination. Git Branches, commits, tags and a CI pipeline triggered by a push. A shell You can run commands, read exit codes and follow a log stream. Not assumed Any prior Docker, Kubernetes, Linux internals or cloud platform experience. Containers and Orchestration: Docker to Kubernetes 3