Became a Kubestronaut: CKS Was the Final Step
I officially became a Kubestronaut, with CKS as the final certification that completed the Kubernetes track.
Introduction
I passed the CKS exam.
This one means a lot to me, not just because CKS is tough, but because it was my final certification in the Kubernetes track. With this, I completed CKA, CKAD, KCNA, KCSA, and now CKS.
That means I am officially a Kubestronaut now.
Why CKS Felt Different
CKS is not the kind of exam where you can memorize a few commands and get through. It is practical, time-pressured, and security-focused. You need to think clearly while working fast.
Compared to the other exams, this one pushed me the most in areas like:
- Hardening clusters and nodes
- Locking down workloads and permissions
- Securing the supply chain and images
- Investigating runtime behavior and audit signals
Honestly, it felt very close to real production incidents: limited time, multiple moving parts, and no room for guesswork.
Exam Prep Strategy
I kept my prep simple and practical. Most of my study time went into hands-on labs and scenarios instead of only reading theory.
The resources I used the most were:
Doing these repeatedly helped me build speed, confidence, and a better troubleshooting flow.
Exam Day Experience
In all honesty, time management was the hardest part.
I ran short of time and could not complete 1 question out of the 16 total questions. I still passed with 85%, but this exam reminded me that time management is absolutely crucial.
The technical part is important, but finishing tasks under pressure is what really decides your result.
Learning Outcomes
The biggest win from this journey was strengthening practical security skills that are useful in day-to-day production clusters.
I got to relearn and work more deeply with tools and practices such as:
- Service mesh and networking security concepts with Istio and Cilium
- Runtime threat detection with Falco
- CIS benchmark checks with kube-bench
- Artifact scanning and SBOM workflows with Trivy and BOM tools
- Security analysis of manifests using tools like kubesec
It was also refreshing to manually harden clusters from scratch. These days, managed Kubernetes providers handle part of the baseline hardening, so doing it manually again was a great way to sharpen core fundamentals.
Final Thoughts
This journey took discipline, many weekends, and a lot of trial and error. But it was worth it.
I am grateful for everything I learned while preparing across all five exams. More importantly, I now feel more confident applying Kubernetes and security skills in real-world environments.
On to the next challenge.