Bootcamp
A two-week sprint to be productive on Kubernetes - from pods to operators.
Bootcamp plan
EXAMPLE
# Kubernetes bootcamp - 10 working days Day 1 - Tooling: kubectl, k9s, kind / minikube, kubeconfig. Day 2 - Core objects: Pod, Deployment, Service, ConfigMap, Secret. Day 3 - Networking: ClusterIP, NodePort, LoadBalancer, Ingress, NetworkPolicy. Day 4 - Workloads: ReplicaSet, StatefulSet, DaemonSet, Job, CronJob. Day 5 - Storage: PVC, PV, StorageClass, ephemeral vs persistent. Weekend project: deploy a 3-tier app (frontend + api + postgres). Day 6 - Probes + rollouts: liveness, readiness, startup, rolling vs recreate. Day 7 - Autoscaling + budgets: HPA, VPA, Cluster Autoscaler, PodDisruptionBudget. Day 8 - RBAC + security: Role/ClusterRole, SA, Pod Security Standards, NetworkPolicy. Day 9 - Helm + Kustomize: when each, anatomy of a chart, overlays. Day 10 - Operators + CRDs: kubebuilder, controller-runtime, where they earn their keep. Capstone: write a tiny operator that watches a CRD and reconciles a Deployment. ## Tips - Always use namespaces; never deploy to default in real clusters - Set resource requests + limits from day one - Use kustomize for envs over helm values when configs diverge - Use k9s daily; it makes kubectl muscle memory faster
Why it matters
Kubernetes is a lot of surface, but a small set of objects covers 95 percent of the work. Build muscle on Deployments + Services + ConfigMaps + RBAC, then add Helm, Operators, and service meshes when you have the problem they solve.
Tip: Tweak the snippet with Try it Yourself », then sit the quiz at the bottom of the page.
Discussion
Loading…