Hands-On Labs
Each week adds constraints to the same cluster storyline. You ship policy bundles, watch them fail in interesting ways, and tune observability hooks. The goal is muscle memory for safe rollouts, not a single perfect YAML file.
Sora Kim
Builds brittle clusters on purpose so you learn to stabilize them calmly.
Shared lab namespaces with per-learner overlays. No shared kubeconfigs outside the classroom boundary.
Examples favor open policy engines, but we map concepts to major cloud policy services in office hours.
Plan for eight focused hours weekly. More if you chase stretch violations.
“Kubernetes Policy Gym scoring rubric made our internal debates less subjective. Still wish week four had one extra office hour for edge cases.”
“The staged violations felt theatrical until they mirrored a real outage pattern we had last quarter.”