GitOps workflow (Argo CD) template
Deploy by pull request: CI builds the image, a config-repo PR bumps the tag, and Argo CD syncs the cluster to match git.
Use this templateFree, opens in your browser. No sign-up.
What's on the board
- App repo + CI
- Developer merges a PR to the app repo · CI: test, build image api:3f9c2a1 · CI opens a PR: bump the tag in overlays/prod
- Config repo (desired state)
- Review + merge (2 approvals for prod) · git revert the bump commit
- Kubernetes cluster (Argo CD)
- Healthy? · Argo CD sees the new commit (webhook) · Sync: apply manifests, wait for rollout · Live state = git
- GitOps principles
- Declarative: the whole system is described in git · Versioned: every change is a reviewed commit · Pulled: the cluster pulls, CI never gets cluster credentials · Reconciled: drift from manual kubectl edits is reverted
Table columns: Config repo path, Contents.
How to use this template
- Click Use this template. It opens in the Kelvo app as a new board, saved in your browser.
- Double-click any box to change its text. Replace the examples with your own content.
- Link by dragging. Hover a box and drag one of its dots onto another box. The whole box is the target, and links stay attached when you move things.
- Sketch, then convert. Draw boxes and arrows with the pen, select the strokes and click Convert sketch: they become real boxes and links.
- Group by environment or region. Draw a frame (F) around a group of services; moving the frame moves everything inside it.
Good for
- gitops
- argo cd
- kubernetes
- devops
- deployment
- Design reviews and architecture decision meetings
- Runbooks and onboarding for on-call engineers
- Planning a migration or a cost-cutting pass
Related templates
Kubernetes cluster overview
Ingress, services, deployments and pods in a namespace, with config, storage, control plane and add-ons around them.
CI/CD pipeline with quality gates
From pull request to production: build, tests, security scans, staging, approval and canary release, with the gates in between.
Canary & blue/green deployment
Release safely: shift a little traffic to the new version, check SLOs, then promote or roll back — plus a strategy comparison.
Infrastructure-as-code workflow
The Terraform change workflow: branch, checks, plan on the PR, review, merge, apply with locked state, and drift detection.
Observability stack
Metrics, logs and traces through OpenTelemetry into Prometheus, Loki and Tempo, with Grafana, alerting and SLO notes.
Release process checklist
From code freeze to 100% rollout: the go/no-go gate, canary checks, rollback path and a checklist for every phase.