Enterprise GitOps Kubernetes Pipeline: ArgoCD & Terraform

Modern enterprise software delivery requires declarative, version-controlled infrastructure where Git is the single source of truth.

This implementation case study documents how Suraj Kumar designed a GitOps automated continuous delivery model for a enterprise client managing 150+ microservices on AWS EKS and Azure AKS.

---

GitOps Architecture Flow

[Developer Commit] ---> [GitHub Repo: app-manifests]

                                |

                   [ArgoCD Controller Sync]

                                |

             +------------------+------------------+

             |                                     |

    [Primary EKS Cluster]                [Secondary AKS Cluster]

             |                                     |

  [Istio Canary Traffic 10%]             [Istio Canary Traffic 90%]

             |                                     |

  [Prometheus Metric Check] ------------> [Auto-Promote to 100%]

---

ArgoCD Application Definition

apiVersion: argoproj.io/v1alpha1

kind: Application

metadata:

  name: epifive-core-payments

  namespace: argocd

spec:

  project: default

  source:

    repoURL: 'https://github.com/epifive-consulting/enterprise-manifests.git'

    targetRevision: HEAD

    path: kustomize/overlays/production

  destination:

    server: 'https://kubernetes.default.svc'

    namespace: production-payments

  syncPolicy:

    automated:

      prune: true

      selfHeal: true

    syncOptions:

      - CreateNamespace=true

---

Business Value Delivered

• Deployment Frequency: Increased from bi-weekly manual releases to 25+ automated daily deployments.
• Rollback SLA: Instant automated rollback (<4 seconds) upon HTTP 5xx error rate spikes >0.1%.
• Developer Productivity: Zero manual SSH / kubectl access needed in production environments.