| Both sides previous revision Previous revision | |
| public:99_annexes:annex-b-terms-and-definitions:g:gitops [2026/09/12 17:42] – ↷ Page moved from private:99_annexes:annex-b-terms-and-definitions:g:gitops to public:99_annexes:annex-b-terms-and-definitions:g:gitops nick_dido | public:99_annexes:annex-b-terms-and-definitions:g:gitops [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido |
|---|
| ====== Git Operations (GitOps) ====== | ====== Git Operations (GitOps) ====== |
| |
| [[private:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]] | [[public:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]] |
| |
| ===== Discussion ===== | ===== Discussion ===== |
| |
| Git Operations (GitOps) applies [[private:99_annexes:annex-b-terms-and-definitions:g:git|Git]] and [[private: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. | 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 [[private:99_annexes:annex-b-terms-and-definitions:v:version_control_system|Version Control System]] contains the authoritative declaration of the desired operational state. | 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: | GitOps applies four core principles: |
| * Reviewable changes | * Reviewable changes |
| * Rollback targets | * Rollback targets |
| * [[private:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]] | * [[public:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]] |
| * [[private:99_annexes:annex-b-terms-and-definitions:r:reproducibility|Reproducibility]] | * [[public:99_annexes:annex-b-terms-and-definitions:r:reproducibility|Reproducibility]] |
| * [[private:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] | * [[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. | 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. |
| The term **GitOps** combines **Git** and **Operations**. | The term **GitOps** combines **Git** and **Operations**. |
| |
| GitOps uses [[private: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 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 [[private: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 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 [[private: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 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: | GitOps does not require a particular: |