DevOps11 min readMay 6, 2026

GitOps with ArgoCD: From Messy Pipelines to Declarative Deployments

B

BADJO Dibéa Koffi

Published on May 6, 2026

The Jenkins Era

Our pipeline was 2,000 lines of Groovy across 12 Jenkinsfiles. Each microservice had subtle differences. When a deployment failed at 2 AM, fixing it took 30 minutes of SSH and manual kubectl commands.

What Is GitOps?

Git is the single source of truth. The desired state of your cluster is declared in Git. ArgoCD continuously reconciles actual state with desired state.

ApplicationSet: One Template, All Services

apiVersion: argoproj.io/v1alpha1
kind: ApplicationSet
metadata:
  name: microservices
spec:
  generators:
    - git:
        repoURL: https://github.com/our-org/k8s-manifests
        revision: main
        directories:
          - path: services/*
  template:
    metadata:
      name: "{{path.basename}}"
    spec:
      source:
        repoURL: https://github.com/our-org/k8s-manifests
        path: "{{path}}"
      destination:
        server: https://kubernetes.default.svc
        namespace: "{{path.basename}}"
      syncPolicy:
        automated:
          prune: true
          selfHeal: true