Canary & blue/green deployment template
Release safely: shift a little traffic to the new version, check SLOs, then promote or roll back — plus a strategy comparison.
Use this templateFree, opens in your browser. No sign-up.
What's on the board
Table columns: Strategy, How it works, Rollback, Extra cost.
- v2 at 100%, retire v1
- Promote: 25% → 50% → 100%
- Analyze 15 min: errors, p95, saturation
- Within SLO?
- Deploy v2 to 5% of traffic
- Automatic rollback to v1
- Investigate, fix, redeploy
- v1 (stable)
- Load balancer / service mesh
- v2 (canary)
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
- devops
- deployment
- canary
- blue green
- release
- Design reviews and architecture decision meetings
- Runbooks and onboarding for on-call engineers
- Planning a migration or a cost-cutting pass
Related templates
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.
GitOps workflow (Argo CD)
Deploy by pull request: CI builds the image, a config-repo PR bumps the tag, and Argo CD syncs the cluster to match git.
Kubernetes cluster overview
Ingress, services, deployments and pods in a namespace, with config, storage, control plane and add-ons around them.
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.
MoSCoW prioritization
Split a release's scope into Must, Should, Could and Won't-have-this-time so everyone agrees what ships.