Safe Delivery: Infrastructure, Pipelines and Kubernetes
Take a change from reviewed infrastructure through artifact promotion and Kubernetes rollout. Test identity boundaries, recovery paths and a Gateway migration.
Take a change from reviewed infrastructure through artifact promotion and Kubernetes rollout. Test identity boundaries, recovery paths and a Gateway migration.
Work through the modules in order. Each lesson ends with an exercise and a retrieval check; keep your answers before revealing the explanation. The final project brings the earlier decisions together in a design or incident record you can discuss aloud.
One introductory lesson is public, one lesson opens with free sign-in, and ten require Premium. Progress is a personal reading record. Self-checks and project rubrics do not award a professional certification. All numerical scenarios are teaching fixtures, not reported production results. Commands are read-only or run against local fixtures unless a lesson explicitly describes an optional sandbox.
Start with DevOps Foundations: Trace and Explain a Service if the prerequisites are unfamiliar.
Next course: Incident Response and Reliability Engineering.
When you finish, you can
- Translate a release requirement into behavioral checks, including negative cases and a deliberate failure that demonstrates the check catches the intended defect.
- Design a layered infrastructure test plan that uses mocked providers for configuration behavior and real sandbox tests for permissions and service constraints.
- Distinguish voluntary eviction, rollout behavior and involuntary failures, then review a node-drain plan with readiness and replacement capacity constraints.
- Review a candidate release across artifact identity, schema compatibility, workflow trust and rollout capacity, then write a staged go/no-go decision with recovery triggers.
BEFORE YOU START · Complete DevOps Foundations or be able to trace requests and explain resource limits.
Syllabus
Define the change
Promote the artifact you actually tested. Order schema and code changes for mixed versions. Write release checks that can actually fail.
Build a trusted pipeline
Serialize infrastructure writers and protect state. Restrict deployment identity to the reviewed workflow. Separate Terraform mocks from provider evidence.
Control the rollout
Budget rollout capacity before changing replicas. Keep GitOps ownership clear during emergency changes. Test disruption budgets against actual eviction paths.
Review and rehearse a release
Migrate ingress by testing behavior and permissions. Measure delivery speed alongside failure and rework. Capstone: rehearse a release with conflicting evidence.