đź’¬ HelloG1toro
By Adrian

My Journey to Becoming a Kubestronaut: 2 Down, 3 to Go!

#kubernetes#certification#devops#kubestronaut

Hello world! If you’re reading this, I am currently on a mission to become a Kubestronaut. Yes, that’s a real thing, and no, it does not involve me being shot into physical space in a pod made of YAML. (Though some days, debugging CrashLoopBackOff errors feels exactly like that.)

The CNCF created the Kubestronaut program for those brave (or perhaps slightly unhinged) individuals who pass all five active Kubernetes certifications.

So far, I’ve managed to rack up two of them:

  1. 🚀 KCNA (Kubernetes and Cloud Native Associate) - The gateway drug. “Oh, Kubernetes isn’t so bad,” I thought. “It’s just some abstractions!”
  2. 🛡️ KCSA (Kubernetes and Cloud Native Security Associate) - Where I learned that giving cluster-admin to everyone is, in fact, frowned upon.

The Final Frontier

Now, I’m gazing into the abyss of the remaining three certifications to get that sweet, sweet Kubestronaut jacket:

  • CKAD (Certified Kubernetes Application Developer): Time to prove I can actually deploy things without copying blindly from Stack Overflow. (Okay, maybe just less copying).
  • CKA (Certified Kubernetes Administrator): The big one. The “fix the cluster before the timer runs out” panic attack simulator.
  • CKS (Certified Kubernetes Security Specialist): The boss level. Where I’ll probably spend hours screaming at RBAC policies and AppArmor profiles.

Why do this to myself?

Good question. Beyond the profound joy of mastering the defacto cloud-native operating system, achieving Kubestronaut status is a massive milestone. It’s about deep expertise. Also, let’s be honest, the swag is legendary.

Wish me luck on my journey to the stars (or at least, to a functioning control plane). If I don’t post again in a few months, assume a rogue NetworkPolicy has isolated me from the internet.

May your pods always be Running and your deployments never be Stuck!