Surge Core Academy
Courses catalog Operations rehearsal Spend tiers Field notes Questions hub Studio story Request information
Abstract violet server lights suggesting cluster depth

Kubernetes Practitioner Program · cohort-led

Operate clusters with rehearsal-grade discipline

  • • Translate rollout monitors into human-readable stop rules
  • • Pair observability boards with incident language stakeholders trust
  • • Keep mentor-reviewed artifacts you can reuse at work

Signals we track across cohorts

Mixed metrics—some percentages, some counts—so teams see both breadth and depth without a single vanity number.

18
months of refreshed lab scenarios
62%
alumni reporting calmer rollouts post-capstone
9.1 / 10
mentor clarity on internal exit surveys
140+
hours of guided cluster time logged
7
cities represented in the latest JP-friendly block

Field notes · latest transmissions

Short essays from mentors—no recycled buzzwords, just operations specifics.

Inside the cohort rig

Layered glow is not just visual noise here—it mirrors how we stack safeguards, telemetry, and human checkpoints before traffic moves.

Cluster labs with guardrails

Namespaces ship with quota stories so you feel pressure without risking neighbor teams.

Rollout monitors you can defend

Mentors ask why a gate exists, not only whether it turned green.

Observability-first triage

Logs, metrics, and traces become one narrative before you page anyone.

Incident rehearsal, not theater

Rotating roles keep language honest; scribes learn to capture decisions that actually happened.

From rehearsal to live operations

A horizontal flow—no four identical circles—just explicit verbs.

  1. Anchor — capture the risk story in writing before touching YAML.
  2. Instrument — wire the smallest set of signals that prove user-visible health.
  3. Rehearse — run the rollout twice: once slow, once at target speed with observers.
  4. Ship — promote with a rollback card pinned next to the change record.
  5. Retrofit — update diagrams while memory is fresh; mentors grade the diff.

Featured lanes this quarter

Three different shapes—long cohort, night blocks, and edge rehearsal.

Voices from recent blocks

Formats intentionally mixed—some formal, some clipped, one with a caveat.

“Rollout Safeguards Studio forced us to script halt reasons before widening traffic. Our staging board now mirrors the template from week two.”

Rina · SRE

Edge Delivery Rehearsal Lab finally made latency budgets feel real—simulated delay beat another generic diagram.

Isaac · deployment engineer

Observability-Led Operations Sprint · ★★★★☆
Loved the trace stitching lab; still want more admission webhook time.

Verified learner · survey

“Night School recap audio > another 80-slide deck.”

Hana · Osaka

Three clarifications people ask early

Cohort rhythm

How do live mentor blocks line up with Japan evenings?

Core sessions publish in JST-friendly windows with recordings inside twelve hours. Night School tracks add optional APAC-friendly repeats, but materials stay English-only for cohort consistency.

Cohort rhythm

What if I miss a live lab?

You receive recap notes, the recording, and a make-up checklist. Mentors do not rebuild the entire lab privately—use office hours for targeted gaps.

Labs & access

Do I get root on shared clusters?

Namespaces are isolated with guardrails. Elevated actions run through break-glass scripts we audit for learning safety—not arbitrary root shells.

Open the full questions hub

Download the syllabus packet (PDF)

We email a printable overview with weekly themes, tooling expectations, and mentor response windows—no payment links inside the PDF.

Compose syllabus request

Average reply window: two business days · Next public intake opens 12 June 2026 (JST)