liveBook · Manning

GitOps repository

As explained in Kargo in Action

A GitOps repository is a Git repository whose declarative configuration represents the desired state of an environment.

A GitOps repository stores an environment’s desired state. Kargo writes changes during promotions; Argo CD reads them and reconciles the cluster. section 3.5.1

A promotion moves an image through this workflow:

  • Kargo updates the image tag in an environment’s Kustomize overlay, then commits and pushes the change. section 3.5
  • Argo CD detects the changed environment path and syncs its Application; the cluster then converges to the updated state. section 3.5
  • If a promotion succeeds but the cluster does not change, check that the Application name matches exactly and that Argo CD can access the repository. section 3.6.3
Listing 3.13 GitOps repository layout
demo-gitops/
├── base/
│   ├── deployment.yaml
│   ├── service.yaml
│   └── kustomization.yaml          #1
└── envs/
    ├── dev/kustomization.yaml      #2
    ├── staging/kustomization.yaml
    └── prod/kustomization.yaml

The example layout separates shared base manifests from dev, staging, and prod environment overlays. section 3.5.1

How Kargo in Action covers it

How deep it goes
Shows environment overlays, image-tag commits, reconciliation, and checks for sync failures.
Examples
Uses a demo application with base manifests and dev, staging, and prod overlays.
What you can do after
Apply promotions by having Kargo commit image-tag changes for Argo CD to reconcile.
How it connects
Connects Kargo promotions, Kustomize overlays, Git, and Argo CD reconciliation.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Kargo in Action. The section links point to the parts of the book it draws on.