Kubernetes Learning Resources: A Curated, Opinionated Map

There is an ocean of Kubernetes content. This is a short, high-signal list of the resources that actually move you from "I can copy YAML" to "I understand what the control plane is doing" — organized by what you're trying to accomplish. Each entry says why it earns your time.

---

Learn by doing (the fastest way to real understanding)

• Kubernetes The Hard Way — Bootstrap a cluster by hand, once, with no helper scripts. You will wire up the API server, etcd, the scheduler, controller-manager, and kubelet yourself — and you will never again be fuzzy about what the control plane does or how the pieces fit. Do this even if you only ever use managed clusters.
• killer.sh — The hardest CKA/CKAD/CKS exam simulator available, and the closest thing to the real exam environment. If you're certifying, this is the practice that exposes the gaps a course leaves. (A session is included with the Linux Foundation exam registration.)

Know what you don't know yet

• roadmap.sh/kubernetes — The full Kubernetes skill map as a visual dependency graph. Use it to find your blind spots and sequence your learning, rather than discovering missing fundamentals mid-incident.
• CNCF Landscape & Projects — Every graduated and incubating project ranked by maturity. Before you adopt a tool, check where it sits — graduated projects are battle-tested; sandbox ones are bets. Knowing the ecosystem is half of platform engineering.

Learn from other people's outages

• k8s.af (Kubernetes Failure Stories) — Real, detailed post-incident writeups from real teams. More useful than most courses because it teaches you the failure modes you'll actually hit (and how to avoid them) instead of the happy path.

Observability (start before you think you need it)

• Prometheus docs — The de-facto metrics standard for cloud-native. Learn the data model, PromQL, and alerting here first; observability is not an add-on you bolt on after the first outage.
• Grafana tutorials — Build dashboards that surface problems instead of just looking pretty. Focus on RED/USE method panels and alerting, not decoration.
• OpenTelemetry docs — The vendor-neutral standard for metrics, logs, and traces. Instrument once here and stop learning a new vendor-specific SDK every time you switch backends.

GitOps & progressive delivery

• Flux docs — GitOps done in a composable, controller-first way. Understanding Flux's reconciliation model makes Argo CD click faster, so many people start here.
• Argo Project — Four tools in one ecosystem: Argo CD (GitOps), Argo Rollouts (canary/blue-green), Argo Workflows, and Argo Events. Together they cover declarative delivery and progressive rollouts.

Security (the tools you'll wish you had before the incident)

• Trivy — Scan container images, filesystems, IaC, and configs for vulnerabilities and misconfigurations with one tool. It's free and fast — there's no excuse to skip scanning in CI.
• Falco — Runtime threat detection for Kubernetes: it watches syscalls and flags suspicious behavior (a shell in a container, unexpected network connections) as it happens. This is the thing you wish you'd installed after your first security scare.

Packaging (you'll use it whether you like it or not)

• Helm docs — The Kubernetes package manager. Learn templating, values, releases, and rollbacks properly — sooner or later every real cluster grows charts, so invest in understanding them rather than cargo-culting.

---

A suggested order

1. Fundamentals — read Kubernetes: Getting Started, then do Kubernetes The Hard Way once.
2. Sharpen — walk the roadmap.sh map and drill weak spots with the interview questions.
3. Operate — wire up Prometheus + Grafana, learn Server-Side Apply, and study a few failure stories on k8s.af.
4. Deliver & secure — add GitOps (Flux/Argo) and scanning (Trivy) + runtime detection (Falco).
5. Certify — if you want the credential, grind killer.sh before your CKA/CKAD/CKS.

External links point to the official docs and well-known community resources. They're maintained by their respective projects, not by DevOpsDrill.

Where to go next

• Practice with the Kubernetes interview questions and the mock interview.
• Avoid classic traps in Memory: MB vs MiB and Server-Side Apply.
• Follow the path in the Kubernetes roadmap.