Gautam Dev

01.

ABOUT

I'm Gautam Dev, a DevOps Engineer with 3–5 years of hands-on experience designing CI/CD pipelines, containerising workloads, and shipping reliable Kubernetes deployments. My goal is simple — automate everything that can be automated.

I specialise in Jenkins, Docker, Kubernetes, and Helm — building systems that build, test, and deploy themselves. I'm a strong believer in GitOps: if it's not in Git, it didn't happen.

Currently holding the CKA (Certified Kubernetes Administrator) certification and actively exploring Prometheus + Grafana observability, ELK logging stacks, and multi-environment AWS EKS deployments.

// Quick Info

Role: Aspiring DevOps Engineer

Certification: CKA — Certified Kubernetes Administrator

Experience: 3–5 Years

Status: Open to Work

Location: India

🔁
GitOps Workflows Argo CD · Helm chart repos · Git as single source of truth
☸️
Kubernetes Operations Cluster management · Rollouts · CKA-level expertise
🐳
Container Pipelines Docker builds · Health checks · Image versioning · Registry auth
☁️
Cloud Infrastructure AWS · EC2 · EKS (planned) · Kind clusters on cloud VMs
📊
Observability (Learning) Prometheus · Grafana · ELK Stack

03.

PROJECTS

PROJECT_01

END-TO-END CI/CD PIPELINE

Jenkins · Docker · Helm · Kubernetes · Node.js

A production-style CI/CD pipeline automating build, test, containerisation, and deployment of a Node.js app — with multi-layer rollback protection and HTML email notifications baked in.

GitHub → Jenkins → Docker Build → Test /health → Push Image → Helm Deploy → K8s Rollout → Auto Rollback

Jenkins Docker Kubernetes Helm Node.js DockerHub GitHub

Health-check testing via /health endpoint with retry logic inside Docker container
Helm atomic deploy with --atomic --timeout 60s for safe rollbacks
Post-deploy validation using kubectl rollout status
Dual-layer rollback: Helm atomic (auto) + manual helm rollback via Jenkins
Image versioning using Jenkins build number for traceable releases
HTML email alerts on success & failure with build metadata & Jenkins link
Secure Docker Hub auth & automatic container cleanup after tests

// Challenges Solved

✗ Deployment reported success even when pods were failing
→ Added kubectl rollout status as mandatory post-deploy gate

✗ Helm couldn't detect image pull failures
→ Combined Helm deploy with rollout status verification

✗ Needed reliable multi-layer rollback
→ Helm atomic flag + Jenkins manual fallback trigger

PROJECT_02

GITOPS CI/CD PIPELINE

Jenkins · Argo CD · Helm · Kubernetes · Flask

A complete GitOps-driven pipeline where Jenkins handles CI (build, test, push), auto-updates Helm chart values, and Argo CD continuously reconciles the Kubernetes cluster to match the desired state in Git.

Dev Push → GitHub → Jenkins CI → DockerHub → values.yaml → GitOps Repo → Argo CD → K8s Cluster

Jenkins Argo CD Helm Kubernetes Flask GitOps Kind EC2

Full GitOps workflow — Git repo is the single source of truth for cluster state
Jenkins builds Docker image, validates via /health check, then pushes to DockerHub
Jenkins auto-updates values.yaml in separate GitOps manifest repo
Argo CD detects Git diff and auto-syncs deployment to Kubernetes
Clean separation: app code repo vs manifest/config repo
Deployed on Kind cluster running on EC2, exposed via kubectl port-forward
Argo CD UI accessible on HTTPS with port-forward for monitoring syncs

// Architecture Highlights

✦ Two-repo structure keeps app code and infra config fully decoupled

✦ Argo CD acts as the continuous delivery layer — no manual kubectl apply needed

✦ Every deployment is auditable — Git history = deployment history

ABOUT

SKILLS

PROJECTS

END-TO-END CI/CD PIPELINE

GITOPS CI/CD PIPELINE

CONTACT

LET'S BUILD
TOGETHER

GAUTAM DEV

ABOUT

SKILLS

PROJECTS

END-TO-END CI/CD PIPELINE

GITOPS CI/CD PIPELINE

CONTACT

LET'S BUILDTOGETHER

LET'S BUILD
TOGETHER