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

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

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.

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

  • Git is the single source of truth for what runs
  • Production changes need a pull request approval
  • Argo CD rolls back by reverting a commit

Prompt used

GitOps flow: a developer merges a pull request, CI runs tests and a security scan, builds and pushes a container image, and opens a pull request in the config repo to update the image tag for staging. Argo CD syncs staging and smoke tests run. If they pass, a promotion pull request for production is approved and Argo CD syncs production; if health checks fail it reverts the commit.

Mermaid code
flowchart TD
  A[Merge pull request to main] --> B[CI: tests and security scan]
  B --> C{Passed?}
  C -->|No| X[Notify developer]
  C -->|Yes| D[Build and push image]
  D --> E[Update staging tag in config repo]
  E --> F[Argo CD syncs staging]
  F --> G{Smoke tests pass?}
  G -->|No| X
  G -->|Yes| H[Open production promotion PR]
  H --> I[Approval by release owner]
  I --> J[Argo CD syncs production]
  J --> K{Health checks OK?}
  K -->|Yes| L[Release done]
  K -->|No| M[Revert commit, Argo CD rolls back]

Inside this diagram

A flowchart with 11 steps, 3 decisions and 14 connections.

Steps

  • Merge pull request to main
  • CI: tests and security scan
  • Notify developer
  • Build and push image
  • Update staging tag in config repo
  • Argo CD syncs staging
  • Open production promotion PR
  • Approval by release owner
  • Argo CD syncs production
  • Release done
  • Revert commit, Argo CD rolls back

Decisions

  • Passed?
  • Smoke tests pass?
  • Health checks OK?

Flow

  • Merge pull request to main β†’ CI: tests and security scan
  • CI: tests and security scan β†’ Passed?
  • Passed? β†’ Notify developer: No
  • Passed? β†’ Build and push image: Yes
  • Build and push image β†’ Update staging tag in config repo
  • Update staging tag in config repo β†’ Argo CD syncs staging
  • Argo CD syncs staging β†’ Smoke tests pass?
  • Smoke tests pass? β†’ Notify developer: No
  • Smoke tests pass? β†’ Open production promotion PR: Yes
  • Open production promotion PR β†’ Approval by release owner
  • Approval by release owner β†’ Argo CD syncs production
  • Argo CD syncs production β†’ Health checks OK?
  • Health checks OK? β†’ Release done: Yes
  • Health checks OK? β†’ Revert commit, Argo CD rolls back: No

Make your own diagram like this

Describe your own system in plain English and CloudSketch AI draws it in seconds. See all AI diagram generators.

Related templates

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.

C4 ArchitectureProDevOps & SRE

Internal Developer Platform

A self-service platform for developers: a Backstage portal with templates that create repos, pipelines and environments without tickets to the ops team.