Below you will find pages that utilize the taxonomy term “Learning”
Posts

read more
How To Learn Kubernetes In 2026, Leveraging AI
TL;DR
- You need four things, nothing more: a laptop, AI, time, and commitment. No budget, no cohort.
- Build one small reference app first (Python + PostgreSQL). Prove it runs standalone, then in Docker. This is a requirement, not optional, and you deploy this same app at every level.
- Get the AI to draft a personal learning plan around that app, not a generic course. Tell it your background, your hours per week, and whether certification matters to you.
- Certification (CKA/CKAD) is optional. It may help with jobs or promotions, it costs money and time, and this series doesn’t require it either way.
- Learn through AI Q&A, not lectures: get quizzed, explain concepts back, get pushed on guesses.
- Round it out with YouTube for what needs to be seen, AI-generated diagrams mid-conversation, and the official Kubernetes docs, which are better as a learning tool than most people realize.
- Turn the AI’s draft plan into real commitments with a “done” bar per level.
- Prompt for learning, not answers: put the first attempt on yourself, use the AI to check it.
- Take notes in your own words, and draw diagrams, on paper or in a tool like Excalidraw.
- Type new YAML and commands yourself instead of copy-pasting; it’s where you catch mistakes.
| Level | Environment | Depends on |
|---|---|---|
| 1 | Minikube on a laptop | Nothing, this is the starting point |
| 2 | A hand built multi VM cluster | Level 1’s kubectl basics |
| 3 | A self managed cluster on AWS EC2 | Level 2’s cluster-bootstrap mechanics |
| 4 | EKS | Level 3’s AWS familiarity |
What This Actually Takes
You need four things to learn Kubernetes this way, and nothing beyond them: a laptop, access to AI, time, and commitment. No budget line, no employer-sponsored training slot, no waiting for a cohort to start.