Back to glossary

GitOps

An operational framework where Git repositories serve as the single source of truth for infrastructure and application configuration, with automated agents ensuring the live environment matches the declared state.

GitOps extends infrastructure as code by making Git the operational control plane. All changes to infrastructure and application configuration are made through pull requests. Automated agents (like ArgoCD or Flux) continuously monitor the Git repository and reconcile the live environment to match the declared state, automatically applying any drift corrections.

The workflow is straightforward: a developer opens a pull request to change a Kubernetes manifest, the change is reviewed and merged, and the GitOps agent detects the change and applies it to the cluster. Rollbacks are as simple as reverting the Git commit. The entire history of every infrastructure change is captured in the Git log.

For AI teams, GitOps provides auditability and reproducibility for model deployments. Model versions, serving configurations, feature flag states, and pipeline definitions all live in Git. This means you can answer questions like "what model was serving traffic last Tuesday" by examining the Git history, and you can reproduce any previous system state by checking out that commit.

Related Terms