Hands-on Labs

GKE Gateway API canary: classroom-sized traffic split

16 min read · Lab

Walkthrough covers Gateway resources, health checks, and how we tear routes down automatically after six hours. Mentors use the same YAML in screen shares.

Tuition reference: KRW 2,200,000

What is inside

Helm values trimmed for 10 rps ceilings
Gateway vs Ingress decision tree
Automatic teardown cron sample
Notebook for diffing declared vs live routes
Smoke test script with friendly output
Incident record template if a canary misroutes
Office-hour debugging script

Outcomes you can show

You can apply a canary without touching unrelated namespaces
You can explain when to pause a rollout
You can capture a concise incident record

Responsible editor

Haneul Park

Technical Lab Engineer who maintains shared GKE classrooms.

Participant notes

“Teardown cron alone saved our moderators twenty minutes each lab night.”

Dorian

Brief FAQ

Most steps yes; we flag the two Autopilot caveats explicitly.