Skip to content
GitOps workflow diagram with repositories, CI pipeline, container registry, GitOps agent and staging and production clusters on a card over a photo

GitOps Workflow Diagram

Presentation template for Google Slides and PowerPoint

Make a copy in Google Slides
Price
Free
Slides
5
Difficulty
Intermediate
Updated
November 8, 2026

Every slide (5)

Overview

A developer merges a pull request into the application repository, which starts the CI pipeline. CI runs tests, builds the container image and scans it, then pushes the image to the registry tagged with the commit SHA. CI then commits the new image tag to the config repository, using a pull request for production. The GitOps agent in each cluster sees the change and applies it to staging at once. After the production change is approved and merged, the same agent applies it to the production cluster.

Making Git the only route to change keeps the clusters auditable. Nobody runs kubectl apply by hand in production, and every change has an author and a review. Rollback becomes a revert of the commit that changed the image tag, and the agent does the rest. Teams wanting more gates can add a promotion stage between staging and production, or require signed images before the agent pulls them.

Useful for

  • Moving a team from manual kubectl deploys to Git-driven releases
  • Adding a reviewed approval step before production rollouts
  • Rolling back a bad container release with a single commit revert

What's included

  • A designed cover slide
  • The diagram: 10 components and 9 connections as editable shapes
  • A components table and the 7-step data flow
  • A legend with notes
  • The same diagram as a draw.io (diagrams.net) file

How to use it

  1. 1

    Click Make a copy in Google Slides, then confirm on the Google page. The copy is saved to your own Google Drive.

  2. 2

    Rename Developer, App repository, CI pipeline and the other boxes inside Code and build to your own components, and delete the ones your system does not have.

  3. 3

    Rewrite the 7-step data flow and the 7-row components table so they match the arrows you keep.

  4. 4

    For the draw.io version, download gitops-workflow-diagram.drawio and open it at app.diagrams.net.

What you need

Requirements

  • A Google account for Google Slides, or the free draw.io (diagrams.net) editor

Works with

  • Google Slides
  • Microsoft PowerPoint (File → Download → .pptx)
  • draw.io / diagrams.net (.drawio file)

Questions

What is the difference between push and pull deployment?

In a push model, the CI system connects to the cluster and applies the changes. In a pull model, an agent inside the cluster watches a Git repository and applies what it finds. The pull model needs no cluster credentials outside the cluster, so access stays narrower.

Why use a separate config repository instead of the app repository?

Keeping manifests apart from source code means a config change does not need a code build, and a code change does not silently alter production. It also gives the operations team its own review history for deployments.

How does GitOps handle configuration drift?

The agent compares the live cluster with the desired state in Git at a regular interval. If someone changes a resource by hand, the agent reverts it to match Git. Manual fixes therefore last only until the next sync.

  • #infrastructure-diagram
  • #architecture-diagram
  • #google-slides
  • #drawio
  • #diagram-template
  • #free-template

More infrastructure diagram templates

See all 9

Also in Developer workflows

All developer workflows templates
Get this template

Preparing your template…