Case study · Cloud infrastructure

Production-Ready EKS Cluster with GitOps

A Kubernetes platform that runs the same GitOps stack on a laptop (Minikube) and on AWS EKS, with Argo CD, Vault, Prometheus and Grafana.

Source on GitHub ↗

How it fits together

  1. Git
    • argo-apps/
    • helm-charts/
    • terraform/
  2. CI (GitHub Actions)
    • validate
    • terraform plan
    • security scan
    • daily drift check
  3. Argo CD
    • App of apps
    • automated sync
  4. Cluster
    • Minikube or EKS (3 AZs)
    • Vault
    • Prometheus + Grafana
    • web app

The problem

Teams want a production-like Kubernetes platform to learn and test on, but a real EKS cluster costs money and takes about an hour to build. The goal was one Git repository that brings up the same stack locally in about 25 minutes and on AWS when it is needed.

What I built

Decisions

What went wrong: The Prometheus CRD that was too big

Syncing the Prometheus stack failed with "metadata.annotations: Too long: may not be more than 262144 bytes". Kubernetes limits annotations to 256 KB, and large inline Helm values in the Argo CD Application pushed the CRD over it. The fix was to move the values into external values files in Git. It is now in the troubleshooting guide.

What I would improve next

AWS EKSTerraformArgo CDHelmVaultPrometheusGrafanaGitHub Actions

← All projects