Skip to content

Latest commit

 

History

History
38 lines (25 loc) · 1.82 KB

README.md

File metadata and controls

38 lines (25 loc) · 1.82 KB

State Synchronization (GitOps)

There are four GitOps Principles:

1-Resources Are Defined Declaratively A system managed by GitOps must have its desired state expressed declaratively.

2-Resource Definitions Are Versioned and Immutable The desired state is stored in a way that enforces immutability, enforces versioning, and retains a complete version history. Usually, Git is used for this.

3-Resource Definitions Are Pulled Automatically Software agents automatically pull the desired state declarations from the source. Here 'software agents' refers to the GitOps tool and, again, the source is usually Git.

4-The Desired State Is Continuously Reconciled With the Actual State Software agents (GitOps tools) continuously observe the actual system state and attempt to apply the desired state.

Choice 1: Argo CD

What Is Argo CD?

Choice 2: Flux

Flux CD v2 With GitOps Toolkit - Kubernetes Deployment And Sync Mechanism What the Flux?! GitOps at Your Fingertips

Choice 3: Carvel kapp-controller

What Is Carvel kapp-controller?

What Is Your Choice?

  • Argo CD
  • Flux
  • Carvel kapp-controller has not yet been implemented. Please let us know (by opening an issue) if you would like to contribute the implementation.