# Why I’m Pursuing CKAD After Becoming a CKA Passing the [Certified Kubernetes Administrator (CKA)](https://www.credly.com/badges/e72821a9-97a5-4ee8-a7f6-93f40246e864/public_url) was one of the most rewarding milestones in my cloud-native journey. The certification challenged me to understand Kubernetes from an administrator’s perspective: * Cluster architecture * Networking * Storage * Security * Troubleshooting * Cluster maintenance It taught me how Kubernetes works. It taught me how to operate Kubernetes. Most importantly, it taught me how to think under pressure when things break. But after earning my CKA and reflecting on my learning journey, I realized something important: > *Knowing how to operate Kubernetes is only one side of the story.* The other side is understanding how applications are designed, deployed, configured, and managed inside Kubernetes. And that’s exactly why I’ve decided to pursue the Certified Kubernetes Application Developer (CKAD) certification. ## **The CKA Changed How I View Kubernetes** Before preparing for the CKA, Kubernetes felt like a massive collection of YAML files, commands, and concepts. By the end of my preparation, I understood: * How Pods communicate * How Services expose applications * How Storage works * How to troubleshoot cluster issues * How to manage Kubernetes resources The CKA gave me a strong operational foundation. But it also revealed a gap in my knowledge. I understood the platform. I wanted to better understand the applications running on the platform. ## **Kubernetes Is More Than Infrastructure** One of the biggest realizations I had during my CKA journey was this: Most users don’t care about Kubernetes. They care about applications. Developers care about: * Deploying applications * Managing configurations * Handling secrets * Scaling workloads * Building reliable services As DevOps engineers, we often focus heavily on infrastructure. But Kubernetes was created to run applications. To truly understand Kubernetes, I believe we need to understand both sides: * The administrator perspective * The developer perspective ## **What the CKA Focuses On** The CKA teaches you how to operate Kubernetes clusters. Typical topics include: ✅ Cluster Maintenance ✅ Networking ✅ Storage ✅ Security ✅ Troubleshooting ✅ Scheduling ✅ RBAC These skills are essential. Without them, clusters become unreliable. But many application-level concepts receive less attention. ## **What the CKAD Focuses On** The CKAD approaches Kubernetes from a different angle. Instead of asking: > *“How do I manage the cluster?”* It asks: > *“How do I build and run applications effectively on Kubernetes?”* Topics include: * Application deployment * Configuration management * Multi-container Pods * Health checks * Jobs and CronJobs * Application observability * Kubernetes design patterns This shift in perspective is exactly what interests me. ## **From Infrastructure Thinking to Application Thinking** One lesson I’ve learned throughout my DevOps career is that great engineers understand both infrastructure and applications. You can build the most reliable Kubernetes cluster in the world. But if you don’t understand: * Application behavior * Deployment strategies * Container design * Configuration patterns you’re only seeing half the picture. CKAD helps bridge that gap. ## **Why This Matters in the Real World** In production environments, problems rarely stay within one domain. A deployment issue might involve: * Application configuration * Secrets * Networking * Resource limits * Storage Understanding both the platform and the workload makes troubleshooting significantly easier. The more I work with Kubernetes, the more I realize that successful engineers don’t think in silos. They understand the complete system. ## **What I’m Most Excited to Learn** As I begin my CKAD journey, these are the areas I’m most excited to explore: ### **Kubernetes Design Patterns** Understanding patterns like: * Sidecar * Ambassador * Adapter ### **Application Lifecycle Management** How applications are deployed, updated, and maintained inside Kubernetes. ### **Health Checks** Learning how readiness, liveness, and startup probes contribute to application reliability. ### **Configuration Management** Using ConfigMaps and Secrets effectively in real-world environments. ### **Multi-Container Applications** Understanding how containers collaborate within Pods. ## **My Goal Is Bigger Than Certification** Just like with the CKA, my goal isn’t simply to pass an exam. The certification is important. But the learning is more important. The objective is to become a better engineer. A better troubleshooter. A better Kubernetes practitioner. A better DevOps professional. CKAD is simply the next step in that journey. ## **Final Thoughts** The CKA taught me how to manage Kubernetes. Now I want to learn how to build on Kubernetes. That’s why CKAD feels like the natural next step. As cloud-native adoption continues to grow, understanding both operations and application development becomes increasingly valuable. For me, this isn’t just about collecting certifications. It’s about becoming a more complete Kubernetes engineer. The journey continues. And CKAD is the next chapter. ## **Connect With Me** If you’re preparing for Kubernetes certifications, pursuing the Kubestronaut journey, or working in the cloud-native ecosystem, I’d love to connect. Follow me for more articles on Kubernetes, CNCF certifications, DevOps, Platform Engineering, and Cloud-Native technologies. LinkedIn: [https://www.linkedin.com/in/shahzadaliahmad/](https://www.linkedin.com/in/shahzadaliahmad/) LFX Profile: [https://openprofile.dev/profile/shahzadahmad91](https://openprofile.dev/profile/shahzadahmad91) Credly: [https://www.credly.com/users/shahzadahmad](https://www.credly.com/users/shahzadahmad) Website: [https://shahzadahmad.dev/](https://shahzadahmad.dev/) If you found this article helpful, consider sharing it with others in the Kubernetes community.