Foundations & Architecture
Why orchestration, the control plane and node components, kubectl, declarative YAML, and running your first local cluster. Start →
Foundations & Architecture
Why orchestration, the control plane and node components, kubectl, declarative YAML, and running your first local cluster. Start →
Workloads
Pods, Deployments and rolling updates, StatefulSets and DaemonSets, and batch work with Jobs and CronJobs. Deploy →
Networking
Services and kube-proxy, cluster DNS, Ingress and the Gateway API, and locking down traffic with NetworkPolicy. Connect →
Storage & Configuration
Volumes, PersistentVolumes/Claims and StorageClasses, ConfigMaps and Secrets, and namespaces with resource quotas. Configure →
Scheduling & Scaling
Requests/limits and the scheduler, affinity/taints/tolerations, the HorizontalPodAutoscaler, and disruption budgets. Scale →
Observability & Security
Liveness/readiness/startup probes, logs and metrics, RBAC and ServiceAccounts, and Pod Security Standards. Secure →
Production & Ecosystem
Packaging with Helm, extending the API with Operators and CRDs, GitOps, and a production checklist with the TypeScript API client. Ship →
The model first, then the manifest
Every topic starts from a model — the reconciliation loop, the Pod, the Service, the scheduler — so Kubernetes’s behavior becomes mechanism you understand, not YAML you copy-paste.
Verified against current API groups
Written against the stable API groups in wide production use today — apps/v1, batch/v1, networking.k8s.io/v1, autoscaling/v2, policy/v1 — and checked against the official docs via context7.
Guarantees, not just YAML
Not “here’s a Deployment” but “here’s what a rolling update actually guarantees, and what a missing readiness probe or PodDisruptionBudget can still let go wrong.” You’ll reason about a cluster with confidence.
Diagrams that explain
The control plane, the reconciliation loop, Service routing, and the scheduling pipeline as theme-aware Mermaid diagrams. Bilingual (English / ไทย) with saved quiz progress.