Are we Already Following All the Commandments?
Explore how Jenkins X aligns with the ten essential GitOps commandments by evaluating which principles are fully implemented and identifying areas needing improvement. Understand how Git repositories drive all changes, ensure reproducibility, and enable asynchronous communication in CI/CD workflows while recognizing processes that still consume resources unnecessarily.
We'll cover the following...
Before we take a break, let’s see how many of the ten commandments we’re following so far.
1. Git is the only source of truth
Everything we did on both the application and the environment level started with a push of a change to a Git repository. Therefore, Git is our only source of truth.
2. Everything must be tracked, actions should be reproducible, and idempotent
Since everything is stored as code through commits and pushes, everything we did is tracked and reproducible due to idempotency of Helm and other tools.
3. Communication between processes must be asynchronous #
Changes to Git fire webhook requests that spin up one or more parallel processes in charge of performing the steps of our pipelines. Hence, communication between processes is asynchronous.