public:99_annexes:annex-b-terms-and-definitions:g:gitops

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
public:99_annexes:annex-b-terms-and-definitions:g:gitops [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1public:99_annexes:annex-b-terms-and-definitions:g:gitops [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== Git Operations (GitOps) ======
  
 +[[public:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
 +
 +===== Discussion =====
 +
 +Git Operations (GitOps) applies [[public:99_annexes:annex-b-terms-and-definitions:g:git|Git]] and [[public:99_annexes:annex-b-terms-and-definitions:d:declarative_configuration|Declarative Configuration]] practices to the operation and management of software systems, applications, infrastructure, or services.
 +
 +In a GitOps approach, a [[public:99_annexes:annex-b-terms-and-definitions:v:version_control_system|Version Control System]] contains the authoritative declaration of the desired operational state.
 +
 +GitOps applies four core principles:
 +
 +  * Declarative
 +  * Versioned and immutable
 +  * Pulled automatically
 +  * Continuously reconciled
 +
 +A GitOps implementation:
 +
 +  * Represents the desired state declaratively
 +  * Records the desired state in a Version Control System
 +  * Identifies each revision of the desired state
 +  * Detects changes to the recorded desired state
 +  * Retrieves approved changes automatically
 +  * Compares the actual operational state with the desired state
 +  * Reconciles differences between the actual state and the desired state
 +  * Reports reconciliation status or failure
 +
 +GitOps uses Git repository history to provide:
 +
 +  * Change identification
 +  * Revision history
 +  * Reviewable changes
 +  * Rollback targets
 +  * [[public:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]]
 +  * [[public:99_annexes:annex-b-terms-and-definitions:r:reproducibility|Reproducibility]]
 +  * [[public:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]
 +
 +Within Crucible documentation, GitOps provides an operational approach for applying approved Declarative Configuration from Git repositories to managed environments and reconciling those environments with the recorded desired state.
 +
 +===== Definition =====
 +
 +//operational approach that records declarative desired state in a Version Control System and automatically reconciles actual operational state with that desired state//
 +
 +===== Source =====
 +
 +Adapted from:
 +
 +  * OpenGitOps, //GitOps Principles//
 +  * Cloud Native Computing Foundation, //Cloud Native Glossary: GitOps//
 +
 +===== Note =====
 +
 +The term **GitOps** combines **Git** and **Operations**.
 +
 +GitOps uses [[public:99_annexes:annex-b-terms-and-definitions:g:git|Git]] as the conventional Version Control System, but its architectural principles depend on controlled versioning, immutability, automatic retrieval, and continuous reconciliation rather than on a particular repository-hosting product.
 +
 +GitOps differs from a general Git-based [[public:99_annexes:annex-b-terms-and-definitions:w:workflow|Workflow]]. A Git-based Workflow uses Git to coordinate work. GitOps additionally requires declarative desired state and automated reconciliation of actual state with that desired state.
 +
 +GitOps differs from a [[public:99_annexes:annex-b-terms-and-definitions:c:ci_cd_pipeline|CI/CD Pipeline]]. A CI/CD Pipeline builds, tests, packages, or delivers changes. A GitOps mechanism observes approved desired state and reconciles an operational environment with that state. A CI/CD Pipeline and a GitOps mechanism can participate in the same Workflow.
 +
 +GitOps does not require a particular:
 +
 +  * Git-hosting service
 +  * Repository provider
 +  * Branch strategy
 +  * Reconciliation tool
 +  * Deployment platform
 +  * Infrastructure provider
 +
 +===== Example =====
 +
 +An approved change to Declarative Configuration is merged into a designated Git branch. A GitOps mechanism detects the new repository state, retrieves the change, compares the declared desired state with the actual deployment state, applies the required changes, and reports the reconciliation result.
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>