Module 01 · 3 lessons
Container artifact and runtime boundaries
Trace reviewed source into an immutable OCI artifact, registry, runtime bundle, and least-privileged Java process.
14 reading lessons · 1 deterministic capstone
Follow one Spring order service from an immutable OCI image through traffic, capacity, rollout, evidence, and verified business recovery.
Five ordered modules · approximately 5 hours
Stable Kubernetes and OCI contracts form the core. Version-sensitive behavior stays cited and explicitly bounded.
Module 01 · 3 lessons
Trace reviewed source into an immutable OCI artifact, registry, runtime bundle, and least-privileged Java process.
Module 02 · 3 lessons
Connect controllers, Services, configuration, identity, probes, traffic eligibility, and graceful application termination.
Module 03 · 5 lessons
Budget JVM and dependency resources, distribute failure domains, and scale from signals without inventing capacity.
Module 04 · 3 lessons
Coordinate mixed-version rollout, collect safe evidence, mitigate reversibly, and verify customer and durable-state recovery.
Module 05 · Capstone lab
Run six deterministic readiness, surge, termination, stall, and capacity scenarios without contacting a cluster.
Browser-only capstone
The lab explains readiness, surge, unavailability, termination, and modeled capacity. It is not a benchmark, calculator, dry-run, or production verification.
Course library
Progress remains local to this browser and every lesson keeps one canonical URL.
Cloud Native Aug 18, 2026 3 min read
Trace a Spring backend from source and OCI image through Kubernetes rollout, traffic, capacity, evidence, and verified recovery.
Cloud Native Aug 18, 2026 3 min read
Separate OCI image, distribution, runtime, registry, CRI, containerd, Docker, and Kubernetes responsibilities in a production release.
Cloud Native Aug 18, 2026 3 min read
Build minimal, non-root, traceable backend images with multi-stage Dockerfiles, immutable promotion, SBOMs, scanning, and signatures.
Cloud Native Aug 18, 2026 3 min read
Connect Pods, ReplicaSets, Deployments, Services, selectors, and EndpointSlices without confusing restart, replacement, or routing evidence.
Cloud Native Aug 18, 2026 3 min read
Separate application configuration, Kubernetes Secrets, rotation, Spring property precedence, and workload identity without leaking credentials.
Cloud Native Aug 18, 2026 3 min read
Design startup, liveness, readiness, EndpointSlice removal, SIGTERM, preStop, and Spring graceful shutdown as separate lifecycle controls.
Cloud Native Aug 18, 2026 3 min read
Connect Kubernetes CPU and memory policy to scheduling, throttling, OOM termination, JVM memory, connection pools, and downstream capacity.
Java Aug 19, 2026 4 min read
Separate Java heap, HotSpot native memory, metaspace, buffers, stacks, RSS, and container OOM evidence with Java 25 NMT.
Java Aug 19, 2026 5 min read
Turn JVM performance hypotheses into controlled canary changes with representative load, rollback, resource budgets, and user-outcome verification.
Cloud Native Aug 18, 2026 3 min read
Use topology placement, affinity, taints, disruption budgets, and eviction evidence without mistaking replica count for business availability.
Cloud Native Aug 18, 2026 3 min read
Reason about HPA metrics, requests, startup delay, stabilization, custom signals, dependency limits, and overload before changing replicas.
Cloud Native Aug 18, 2026 3 min read
Coordinate immutable images, surge, unavailability, readiness, termination, rollback, and compatible database change in a backend rollout.
Cloud Native Aug 18, 2026 3 min read
Trace user impact through workload state, Pod events, container reasons, metrics, logs, traces, dependencies, and durable business evidence.
Cloud Native Aug 18, 2026 3 min read
Diagnose Pending, image pull, crash, probe, OOM, rollout, capacity, and dependency failures from user impact to verified recovery.
Cloud Native Aug 18, 2026 3 min read
Run six deterministic browser scenarios for rollout capacity, slow readiness, stalled updates, termination risk, and version regressions.
FAQ
No. Manifests and commands are explanatory. The capstone is a deterministic browser model and neither connects to nor changes a cluster, registry, cloud account, or paid service.
No. It is a production backend operations path for engineers who already understand Java, Spring, HTTP, and basic backend architecture.
No. Controller convergence must be followed by user, dependency, migration, asynchronous, and durable business-state verification.
No. Its steps and per-Pod capacity are explicit teaching inputs, not measurements, benchmarks, forecasts, or deployable advice.