DEV Community: Kapil Bhalodiya

🚀 How I Passed the CKAD Exam

Kapil Bhalodiya — Thu, 17 Jul 2025 05:19:48 +0000

Real-world preparation tips, resources, and practice scenarios to crack the Kubernetes CKAD certification

Passing the Certified Kubernetes Application Developer (CKAD) exam was a big milestone in my DevOps journey. This blog post is a complete guide based on my real-world experience—designed to help you succeed in your first attempt too.

🧠 What is CKAD?

The CKAD exam tests your ability to design, build, and run applications on Kubernetes. It's hands-on, performance-based, and 2 hours long, with about 15-20 scenario-based questions.

Key areas it covers:

Pod design
Configuration
Multi-container pods
Observability
Services & Networking
State persistence

⏳ My Preparation Timeline

Week	Activity
1–2	Understand exam structure, set up local lab
3–4	Practice each topic using `kubectl` and YAML
5–6	Attempt mock exams, simulate real exam conditions
7	Final revision, focus on speed & shortcuts

🛠️ My Study Resources

📘 Courses

📚 Docs You Should Bookmark (Yes, you can use them during the exam!)

🧪 Practice Labs

KodeKloud Labs
Github Exercise
Killer.sh Simulator – official practice simulator

💡 Pro Tips That Helped Me

1. Master `kubectl` Autocomplete

source <(kubectl completion bash)
alias k=kubectl
complete -F __start_kubectl k

2. Use Imperative Commands

Example:

kubectl create deployment nginx --image=nginx --dry-run=client -o yaml > nginx.yaml

Saves time and helps avoid YAML syntax errors.

3. Keep a Notebook of Common Snippets

I created a personal cheat sheet of YAML templates for:

Pods
Deployments
Services
ConfigMaps
Secrets
PersistentVolumeClaims

4. Practice Fast File Navigation

Use:

cd /etc/kubernetes/manifests/
vi myfile.yaml

Also:

Use :set number in Vim
Copy-paste YAML snippets smartly using mouse or middle-click

🎯 Exam Strategy

Start with the easiest questions first
Skip long multi-step tasks and come back later
Use bookmarks (CTRL+F) to search within docs fast
Always validate your answers using:

kubectl get <resource> -o yaml

📦 My Lab Setup

Ubuntu VM (min 2 CPU, 4GB RAM)
Minikube or KIND (Kubernetes IN Docker)
VSCode + terminal
tmux or split terminal view

🎉 Final Thoughts

Cracking the CKAD exam was not just about knowing Kubernetes—it was about becoming confident in using it practically.

If you're aiming for the exam:

“Don’t just study. Simulate. Recreate scenarios and break things—then fix them.”

🧵 Stay Connected

I’m sharing more DevOps + Kubernetes tips on LinkedIn.

Feel free to DM if you're preparing—I'd be happy to help!

🚀 Secure Your Deployments: A DevSecOps + GitOps CI/CD Pipeline with Jenkins, ArgoCD, and Kubernetes

Kapil Bhalodiya — Tue, 15 Jul 2025 16:37:56 +0000

A complete breakdown of how I automated code quality, security, containerization, GitOps deployment, and monitoring — using only open-source tools.

🚀 Why I Built This Pipeline

In today’s cloud-native era, simply deploying code isn’t enough.
We need to:

✅ Ensure code quality
✅ Scan for security vulnerabilities
✅ Automate deployments
✅ Monitor everything
✅ Get feedback instantly

So, I decided to build a DevSecOps + GitOps pipeline that ties together:

🔁 Jenkins for CI/CD

📦 Docker + GitHub + DockerHub

🔍 SonarQube, Trivy, OWASP Dependency Check

☸️ Kubernetes + ArgoCD

📈 Prometheus, Grafana, Loki, Alertmanager

💬 Slack + Gmail notifications

🎥 See It in Action

Watch the pipeline executing:

🧠 Pipeline Flow Breakdown

Let's walk through each step in this real-world production-ready CI/CD setup.

🟢 1. Developer Pushes Code to GitHub

Triggers a Jenkins multibranch pipeline via GitHub webhook

🟡 2. Jenkins CI Begins — With Parallel Security Gates

parallel {
  stage('SonarQube') {
    steps {
      sh 'sonar-scanner -Dsonar.projectKey=my-app ...'
    }
  }
  stage('Trivy Scan') {
    steps {
      sh 'trivy fs . --exit-code 1'
    }
  }
  stage('OWASP Check') {
    steps {
      sh './dependency-check/bin/dependency-check.sh -s .'
    }
  }
}

✅ Code quality, container vulnerabilities, and dependency checks all run in parallel

🔵 3. Docker Build + Push

docker build -t <image-name>:<Image-tage> .
docker push <image-name>:<Image-tage>

Built containers are pushed to DockerHub or any secure private registry.

🟠 4. Jenkins CD Updates Kubernetes Manifests

Jenkins updates the Kubernetes deployment.yaml with the new Docker image:

sed -i -E 's|^(\\s*tag:) .*|\\1 "${imageTag}"|' values.yaml
git commit -am "update image tag"
git push origin main

This commit lands in a separate Infra GitHub Repo, which is continuously watched by ArgoCD.

🔴 5. ArgoCD (GitOps) Deploys to Kubernetes

ArgoCD syncs automatically with the updated manifest repo.
It deploys the new version into the Kubernetes cluster.

🟣 6. Monitoring & Logging Kicks In

Prometheus scrapes metrics from the cluster and app.
Grafana Dashboards display:

Application performance
Pod CPU/memory usage
Business metrics

Loki collects logs
Alertmanager sends alerts on failure, high latency, etc.

📨 7. Instant Notifications

Pipeline stages notify:

✅ Gmail for critical alerts

✅ Slack #ci-cd for success/failure, build times

Example Slack message:

✅ Docker image built and pushed
🚀 ArgoCD deployed version to cluster

🧪 Challenges I Faced

Managing parallel Jenkins stages with proper failure handling
Avoiding secret exposure in git history
Setting up ArgoCD auto-sync correctly
Tuning Prometheus scraping and Grafana alert rules
Handling secure scanning without breaking pipelines

💡 What I Learned

🔐 Security gates should be integrated early (shift-left) in CI

☸️ GitOps brings traceability and rollback safety

📈 Observability is critical for real production setups

📬 Notifications save time during active development cycles

🔗 Try It Yourself

GitHub Infra Repo (with manifests): [https://github.com/Kapil-Bhalodiya/E-Commerce/infra]
ArgoCD app config: [https://github.com/Kapil-Bhalodiya/E-Commerce/infra/config/applications.yaml]

📬 Final Thoughts

This pipeline is more than a pet project — it’s a blueprint for building production-ready, secure, and scalable deployment workflows using only open-source tools.

If you're starting your DevOps journey or want to adopt GitOps at scale, this setup might help you avoid months of trial and error.

💬 Feel free to drop your thoughts, suggestions, or questions in the comments.
I’m open to feedback and collaborations!