CloudSketch AI Logo
FeaturesTemplatesPricingEnterpriseAboutContactLog in
πŸŒ™β˜€οΈ
Log inStart free
Home/Templates/DevOps & SRE

πŸ› οΈ DevOps & SRE Β· Sequence

Canary Release Sequence

How a canary release sends a small share of traffic to a new version, compares its error rate with the stable version, and promotes or aborts automatically.

More DevOps & SRE templates

Opening a template is free and never counts toward your daily diagrams. Asking the AI to change it counts as one.

Drawing diagram…

What this diagram shows

  • Traffic moves in steps: 5, 25, 50, then 100 percent
  • Metrics are compared automatically at each step
  • A bad canary is rolled back without a person stepping in

Prompt used

Canary release with Argo Rollouts: the controller deploys version 2 pods and tells the service mesh to send 5 percent of traffic to them. It queries Prometheus to compare error rate and latency with version 1. If metrics are healthy it increases to 25, 50 and 100 percent. If error rate rises above 1 percent it sets canary traffic to zero and scales version 2 down.

Mermaid code
sequenceDiagram
  participant AR as Argo Rollouts
  participant K as Kubernetes
  participant M as Service Mesh
  participant P as Prometheus
  AR->>K: Create v2 pods
  AR->>M: Send 5% to v2
  loop Each step: 5, 25, 50%
    AR->>P: Compare v2 and v1 errors and latency
    alt Healthy
      P-->>AR: v2 within limits
      AR->>M: Increase v2 share
    else Error rate above 1%
      P-->>AR: v2 failing
      AR->>M: Send 0% to v2
      AR->>K: Scale v2 down
    end
  end
  AR->>M: Send 100% to v2
  AR->>K: Remove v1 pods

Inside this diagram

A sequence diagram with 4 participants and 10 messages, in the order they happen.

Systems

  • Argo Rollouts
  • Kubernetes
  • Service Mesh
  • Prometheus

Steps in order

  • 1. Argo Rollouts β†’ Kubernetes: Create v2 pods
  • 2. Argo Rollouts β†’ Service Mesh: Send 5% to v2
  • 3. Argo Rollouts β†’ Prometheus: Compare v2 and v1 errors and latency
  • 4. Prometheus β†’ Argo Rollouts: v2 within limits (reply)
  • 5. Argo Rollouts β†’ Service Mesh: Increase v2 share
  • 6. Prometheus β†’ Argo Rollouts: v2 failing (reply)
  • 7. Argo Rollouts β†’ Service Mesh: Send 0% to v2
  • 8. Argo Rollouts β†’ Kubernetes: Scale v2 down
  • 9. Argo Rollouts β†’ Service Mesh: Send 100% to v2
  • 10. Argo Rollouts β†’ Kubernetes: Remove v1 pods

Conditions and loops

  • Repeats: Each step: 5, 25, 50%
  • If: Healthy
  • Otherwise: Error rate above 1%

Make your own diagram like this

Describe your own system in plain English and the AI sequence diagram generator draws it in seconds, in the same style as this template.

Related templates

FlowchartDevOps & SRE

GitOps Deployment Flow

How a code change reaches production with GitOps: CI builds and tests, the image tag is written to a config repo, and Argo CD syncs the cluster to match Git.

C4 ArchitectureProDevOps & SRE

Observability Stack (Metrics, Logs, Traces)

A complete observability setup: OpenTelemetry collects metrics, logs and traces from services, which are stored separately and viewed together in Grafana with alerting.

State MachineDevOps & SRE

Incident Lifecycle

The stages of a production incident from the first alert to the postmortem, with severity escalation along the way.

SequenceDevOps & SRE

Incident Response Sequence

Who does what when production breaks: monitoring pages the on-call engineer, an incident channel is opened, customers are updated and the fix is rolled out.

DeploymentProDevOps & SRE

Blue-Green Deployment

A blue-green setup where a new version is deployed next to the live one and traffic is switched only after it passes checks, allowing instant rollback.

FlowchartDevOps & SRE

Infrastructure as Code Pipeline

How infrastructure changes are made safely with Terraform: plan on pull request, policy checks, approval, apply and drift detection.