A platform team implements a GitOps promotion workflow requiring a pull request review from a platform engineer before any change reaches production. Which mechanism best implements this production gate without violating GitOps principles?

Question

Accepted Answer

B. Enable Git branch protection rules with required reviewer approvals on the production configuration path so the GitOps operator only syncs after a reviewed PR merges. Using Git branch protection rules with required reviewers enforces the approval gate through Git's own mechanisms, keeping all state changes in Git per GitOps principles. The ArgoCD production Application watches the protected path and syncs only after a reviewed merge. Option c requires manual CLI intervention outside the GitOps model and creates an operational bottleneck.

A platform team implements a GitOps promotion workflow requiring a pull request review from a platform engineer before any change reaches production. Which mechanism best implements this production gate without violating GitOps principles?

Related Questions

Discussion