Case Study

Multi-Environment EKS GitOps Platform

Built a GitOps-driven, autoscaling EKS platform spanning multiple environments and production teams.

Challenge

Running Dev, Staging and Production Kubernetes environments consistently — with reliable deployments, cost-efficient autoscaling and resilient backups — without a dedicated platform team behind them.

Architecture / Approach

Implemented ArgoCD GitOps workflows across multi-environment EKS clusters, with Karpenter for spot-aware, PDB-respecting node autoscaling. Used Helm charts and CronJobs for application delivery, Velero for cluster backups, and Prometheus/Grafana for metrics and alerting. Managed the underlying AWS resources — S3, Aurora, Secrets Manager — through Terraform.

My Role

Designed the cluster architecture, GitOps workflows and cost-aware autoscaling strategy across environments.

Outcome

Delivered a repeatable GitOps platform pattern used across production EKS clusters, with automated scaling, backups and monitoring in place rather than manual per-environment operations.

Technologies

AWS EKS
ArgoCD
Karpenter
Helm
Velero
Terraform
Prometheus
Grafana

Git Repository

ArgoCD Sync

EKS Clusters (Dev/Stage/Prod)

Karpenter Autoscaling

Next case study

AWS to GCP Infrastructure Migration →