The Problem

Kubernetes is everywhere. And yet, for many developers, it still feels like a black box.

While it has become the backbone of modern infrastructure — powering microservices, jobs, APIs, and real-time applications across the globe — most developers never really get comfortable with it. They use it indirectly, through CI pipelines or deployment platforms, but don't always understand what happens after the code is pushed.

For a technology this central, that's a big problem.

Kubernetes is meant for more than Ops

Kubernetes was not designed to be exclusive to operations teams. From the beginning, it introduced concepts that clearly separate infrastructure concerns from application concerns — and exposes powerful abstractions that developers can safely use.

Objects like IngressClass, StorageClass, ConfigMap, or Service exist precisely so that devs don't have to know the full complexity of the underlying network or storage layer.

But in practice, we've often gone the opposite way.

Kubernetes has been handed over almost entirely to platform and ops teams, while developers are told to "just apply this YAML file" — without much explanation. If something breaks, they escalate. If something doesn't behave as expected, they wait.

Documentation is not enough

Don't get me wrong — Kubernetes has fantastic documentation. It's structured, complete, and deeply detailed.

But learning a complex system like Kubernetes requires more than good docs. It requires practice. You have to break things. Fix them. Read logs. Check events. Try something, fail, and learn from it.

That's where the idea for Kubeasy came from.

What is Kubeasy?

Kubeasy is a learning platform that puts developers in front of realistic Kubernetes problems — and lets them figure it out.

Each challenge is designed like a miniature incident. You're dropped into a local cluster where something isn't working: a Job fails, a Deployment is misconfigured, a NetworkPolicy blocks traffic, a healthcheck crashes the app.

$ kubeasy challenge start networking-basics
✓ Cluster created
✓ Challenge deployed
✓ Ready to debug!

$ kubectl get pods
NAME            STATUS             RESTARTS
backend-XXX     CrashLoopBackOff   5

$ kubectl logs backend-XXX
Error: Connection refused...

# ... investigate, fix, verify ...

$ kubeasy verify
✓ Challenge completed! +50 XP

Everything runs locally

Kubeasy is 100% local. When you start a challenge, it automatically sets up a Kind cluster on your machine, prepares the resources, and runs everything inside an isolated namespace.

• 💸 No cloud billing — Everything runs on your machine
• ⚡ Instant start — No waiting for cloud clusters
• 🔒 Complete privacy — No data leaves your computer
• 🎯 Isolated environments — Each challenge in its own namespace

Open source by design

Kubeasy is open source because it should be. Learning infrastructure shouldn't be a black box.

You should be able to inspect how a challenge works, how a verification is written, how policies are applied. You should be able to suggest new challenges based on real bugs you've seen. All Kubeasy repositories are public on Github :

• kubeasy-cli — CLI tool (Go + Cobra)
• challenges — Challenge repository
• website — This website (Next.js)

Ready to start learning?

Whether you're a dev trying to learn Kubernetes, an SRE tired of answering the same questions, or a team lead looking to level up your engineers — we'd love for you to try Kubeasy.

Let's make Kubernetes less mysterious — one challenge at a time.