Container Orchestration Bundle
Four cheatsheets covering the full container lifecycle: building images with Docker, composing multi-service stacks locally, orchestrating them at cluster scale with Kubernetes, and packaging applications for repeatable deployment with Helm.
Each sheet is designed to be printed and pinned above your desk — the commands you actually use during incidents and deployments, not a re-printed man page.
What's Included
Docker Cheatsheet
- Image lifecycle — build, tag, push, prune, multi-stage builds
- Container operations — run, exec, logs, inspect, stats, stop vs kill
- Volumes and bind mounts — when each is appropriate, backup strategies
- Networks — bridge, host, overlay, and container-to-container DNS
- Dockerfile patterns — layer ordering for cache efficiency, .dockerignore
- Debugging —
docker inspectJSON filtering,docker events, disk usage triage
Docker Compose Cheatsheet
- Service definition syntax — the fields that matter in production
- Environment handling —
.envfiles, variable substitution, secrets - Health checks and
depends_onconditions — real startup ordering - Override files — dev vs staging vs production from one base
- Scaling and resource limits —
deploysection, CPU/memory bounds - Common failure modes — orphan containers, stale networks, volume name clashes
Kubernetes Cheatsheet
- Core objects — Pod, Deployment, Service, Ingress, ConfigMap, Secret
- kubectl patterns — contexts, namespaces,
-o jsonpath, label selectors - Rolling updates and rollbacks —
kubectl rolloutin practice - Debugging — describe, logs, exec, port-forward, ephemeral containers
- Resource management — requests vs limits, QoS classes, node pressure
- RBAC essentials — Role, RoleBinding, and service accounts
Helm Cheatsheet
- Chart structure — Chart.yaml, values.yaml, templates
- Template functions — pipelines, conditionals, ranges, named templates
- Dependencies and subcharts — composing applications from reusable parts
- Release management — install, upgrade, rollback, history
- Values layering — set flags, values files, environment overrides
- Hooks and tests — pre-upgrade jobs, chart verification
Excerpt — Docker Layer Caching
The difference between a 12-second and a 4-minute build is usually layer ordering. Copy your dependency manifests first, install dependencies, then copy source:
# Slow: any source change invalidates the dependency install
COPY . /app
RUN pip install -r /app/requirements.txt
# Fast: dependencies only reinstall when the manifest changes
COPY requirements.txt /app/
RUN pip install -r /app/requirements.txt
COPY . /app
Excerpt — Kubernetes Rollback
# Check rollout history
kubectl rollout history deployment/web -n production
# Roll back to the previous revision
kubectl rollout undo deployment/web -n production
# Pin a specific revision
kubectl rollout undo deployment/web --to-revision=3 -n production
# Watch rollout status until it settles
kubectl rollout status deployment/web -n production --timeout=120s
Choosing Between Docker Compose and Kubernetes
| Signal | Compose | Kubernetes | |---|---|---| | Single host, handful of services | ✔ | overkill | | Need self-healing and autoscaling | — | ✔ | | Team smaller than ~5 engineers | ✔ | consider later | | Multi-node or hybrid cloud | — | ✔ | | CI/CD with blue/green rollouts | possible | ✔ |
Many teams run Compose in staging and Kubernetes in production — the bundle covers both, so the same reference serves each environment.
Related Reading on graphwiz.ai
- Containerized AI Workloads: Multi-Model Management with Docker
- Kubescape 4: Kubernetes Security in the AI Era
Format
- Four PDFs (print-ready, A4), one per tool
- Each sheet fits on one to two pages — designed to print and tape to your wall
- Instant download after purchase
Price
$14.00
Who This Is For
- Developers and DevOps engineers running containerized workloads in staging or production
- Teams adopting Kubernetes who need a quick reference for both Docker and K8s commands side by side
- Anyone who wants printed cheatsheets on the wall instead of context-switching to browser tabs
FAQ
Do the sheets cover Podman or containerd? The Docker sheet targets the Docker CLI, but the majority of commands work identically under Podman's Docker-compatible interface. containerd users typically interact via Kubernetes or nerdctl — the K8s sheet covers that path.
Which Kubernetes version do the examples target?
kubectl 1.29+ syntax. Where older clusters differ (notably kubectl run flags and ephemeral containers), the sheet notes the version boundary.
Are the cheatsheets updated? Yes — the bundle receives updates when major versions shift behaviour. Buyers get re-download access to new revisions through the library page.