Production Blueprint · Industry-standard pattern
GitOps on Kubernetes: the cluster pulls, CI never pushes
The push-based pipeline in the Docker + Kubernetes blueprint has CI reach into the cluster. GitOps flips that: CI stops at the container registry, and an agent inside the cluster (Argo CD) continuously makes the cluster match a Git repository.
GitCI pipelineContainer registryHelmArgo CDKubernetes (AKS / EKS)IngressHPA
Sign in free to read this blueprint
Here is what's inside:
- The GitOps loop
- Promotion is a pull request
- What happens after a merge
- Why each tool sits where it does
- Where GitOps goes wrong
- The interview talk track
- What I'd improve next
Want to see what a full blueprint looks like first? Read: .NET 8 + Angular 20 on Azure Windows VMs