beginner
Kubernetes Cluster Operations
You will configure namespaces, network policies, and resource quotas on a lab cluster, then rehearse failure modes such as node drain and etcd backup checks. The syllabus maps to day-one tasks for platform associates rather than abstract theory.
Logistics
6 weeks · 8h/week · Cohort · ¥98,000 JPY (informational)
Included focus areas
- Hands-on kind/minikube and managed control-plane exercises
- Workload scheduling, probes, and autoscaling walkthroughs
- RBAC templates aligned to least-privilege onboarding
- Ingress + TLS termination patterns with annotated examples
- Packaging exercises with Helm charts you can fork
- Observability hooks: metrics and log labels that stay consistent
- Runbooks for upgrades with rollback checkpoints
Outcomes
- Ship a multi-service demo with health-checked deployments.
- Document a rollback path your teammates can follow.
- Explain quota and limit decisions to non-infra stakeholders.
Responsible instructor
Mika Okada
Former platform lead for a Yokohama fintech cohort program.
FAQ
Do I need a cloud account on day one?
No. Week 1-3 use local clusters; week 4 introduces a temporary sandbox project you can opt out of by pairing with a classmate.
Is certification included?
We map topics to CKA domains but exam vouchers are not part of tuition. You receive a skills checklist instead.
What is intentionally light?
Service mesh deep dives are out of scope; we provide a reading list if you want to continue afterward.
Experience notes
“Week 2 network policy lab finally made taints and tolerations click — I reused the diagram in our internal wiki.”
“Clear pacing, though the Helm module expects you to read ahead. The mentor comments on my values.yaml were worth the time.”