GitOps manages infrastructure changes through declarative infrastructure as code, version control, and continuous deployment. A controller detects drift between the desired configuration and actual state, then reconciles the difference and runs tests. section 7.4
A practical GitOps change typically follows this path:
- Branch or update the declarative configuration. section 7.4
- Commit the change, open a pull request, and run automated checks. section 7.4 section 7.5
- Review and merge the change so continuous deployment applies it and reduces drift. section 7.4
Collaborative infrastructure change
A team proposes an infrastructure update on a feature branch, tests it, adds reviewers, and merges it after approval. Commit and pull-request history records who requested and made the change. section 7.4
Figure 7.20 An implementation of GitOps can use feature-based development to open a pull request, test changes on a branch, add reviewers, and merge the changes.
Shows a feature-based GitOps workflow from branch creation through testing, review, and merge. section 7.4
