World map

 

BM

World K7: Self-Driving

Promote with pull requests

You will learn: how one image moves from staging to production with a reviewed pull request.

Checked with Kubernetes 1.37 on 31 Oct 2026

The problem

Shop 1.5.0 ran fine on staging all day. Now production should get it. What is the GitOps way?

Watch

Tap each point on the timeline.

One image, two folders. To promote: Move the same tested build on to the next environment, like from staging to production. is to move the same image to the next environment.

Try it

Mei opened the promotion PR. Rules say it needs one approval. Review it, then merge.

Practice repo — not a real website
kedai-kancil / gitops
Promote shop 1.5.0 to prod #13
Open mei wants to merge promote-1.5.0 into main
  1. mei

    Staging ran 1.5.0 for a day. No errors.

    Same image, now for prod.

Checks
  • Passed kustomize build
How to merge
Merging is blocked
  • This branch needs one approving review first.
Your review

Try it

Put a safe promotion in order.

First step at the top. Put these in order. Use the arrows, or drag.

  • A teammate approves it
  • Staging runs the new tag
  • Open a PR for the prod folder
  • Checks on staging pass
  • Merge: Argo CD syncs prod

Predict

Prod breaks right after the merge. What is the fastest safe undo?

Check

Some settings differ per environment. Others stay the same in the shared base. Sort them.

Drag a card into a box. Or tap the card, then tap the box.

      You did it!

      You can now promote one image between environments with a pull request.

      Go deeper (optional)

      Prefer one folder per environment over one branch per environment. Folders are easy to compare and never need merging back. Some teams automate promotion with tools like Kargo. Real rep (optional): make envs/staging and envs/prod overlays for Kedai Kancil. Run kubectl kustomize envs/prod to see the result.