My Journey Toward Becoming a Kubestronaut : From CKA to CKS and CKAD

A few years ago, I had no idea that Kubernetes would become such an important part of my professional journey.

Like many engineers, my career started in a completely different space. I began as a Network Engineer, worked with on-premises infrastructure, gradually moved into Cloud Operations, and eventually transitioned into DevOps. Along the way, I kept hearing the same word everywhere: Kubernetes.

At first, Kubernetes felt overwhelming.

Pods, Deployments, Services, Ingresses, RBAC, Persistent Volumes — there seemed to be an endless list of concepts to learn. Every blog, every conference talk, and every job description pointed toward Kubernetes as the foundation of modern cloud-native infrastructure.

I knew that if I wanted to grow as a DevOps Engineer, I needed to move beyond theory and develop real expertise.

The Decision to Pursue CKA

My Kubernetes certification journey began with the Certified Kubernetes Administrator (CKA).

When I first looked at the CKA curriculum, it felt intimidating. Unlike many traditional certification exams, CKA is entirely performance-based. There are no multiple-choice questions. You are placed in a live environment and expected to solve real operational problems.

This was both exciting and terrifying.

I started with the fundamentals:

Kubernetes architecture
Pods and workloads
Networking
Storage
Scheduling
Cluster maintenance
Troubleshooting

My preparation focused heavily on hands-on practice. I spent countless hours creating clusters, breaking them intentionally, and fixing them again. I learned that success in Kubernetes comes less from memorization and more from understanding how different components work together.

The Kubernetes documentation quickly became my best friend.

After weeks of preparation and practice labs, I finally sat for the CKA exam.

Passing the CKA was a huge confidence boost. More importantly, it changed how I approached Kubernetes in my day-to-day work. Concepts that once seemed complicated started making sense.

Taking a Long Pause

Interestingly, I didn’t immediately jump into another certification.

For almost a year, I focused on applying Kubernetes concepts in real-world environments. I worked with cloud infrastructure, automation, CI/CD pipelines, and containerized applications. This practical experience proved just as valuable as certification preparation.

Looking back, this gap helped me more than I realized at the time.

Instead of rushing toward the next badge, I spent time strengthening my foundation.

The Next Challenge: CKS and CKAD

After gaining more hands-on experience, I decided it was time to continue the journey.

This time, I targeted both the Certified Kubernetes Security Specialist (CKS) and Certified Kubernetes Application Developer (CKAD).

Each certification offered a different perspective.

CKAD: Thinking Like a Developer

CKAD shifted my mindset from cluster administration to application delivery.

The focus was on:

Designing applications for Kubernetes
Multi-container pods
ConfigMaps and Secrets
Application troubleshooting
Resource management

It taught me how developers interact with Kubernetes and how applications are built to run effectively inside clusters.

CKS: Security Changes Everything

CKS was arguably the most challenging certification of the three.

Security introduces a completely different layer of complexity.

I spent time learning:

Kubernetes hardening
Pod security
Network policies
Runtime security
Supply chain security
Image scanning and vulnerability management

Preparing for CKS made me realize that operating Kubernetes securely is just as important as operating it successfully.

Three Certifications Down

Today, I hold:

✅ CKA — Certified Kubernetes Administrator

✅ CKAD — Certified Kubernetes Application Developer

✅ CKS — Certified Kubernetes Security Specialist

Each certification taught me something different.

CKA taught me how Kubernetes works.

CKAD taught me how applications run on Kubernetes.

CKS taught me how to secure Kubernetes.

Together, they helped me build a much deeper understanding of the Kubernetes ecosystem.

The Road to Kubestronaut

The ultimate goal is to become a Kubestronaut.

For those unfamiliar with the program, Kubestronaut is awarded to professionals who successfully earn all five major Kubernetes certifications from the CNCF and Linux Foundation ecosystem.

I’m currently three certifications into that journey, with two more certifications remaining.

The finish line is getting closer.

Final Thoughts

If there’s one lesson I’ve learned throughout this journey, it’s this:

Certifications alone don’t make you an expert.

The real value comes from the countless hours spent practicing, troubleshooting, experimenting, and applying what you’ve learned in real environments.

The certifications simply validate that effort.

My journey from Network Engineer to DevOps Engineer and now toward becoming a Kubestronaut has been challenging, rewarding, and filled with continuous learning.

And the journey isn’t over yet.

Two certifications remain.

I’ll be sharing my preparation strategies, lessons learned, resources, mistakes, and experiences in future articles.

See you in the next article.