The principles of GitOps
GitOps has the following key principles:
- It describes the entire system declaratively: Having declarative code forms the first principle of GitOps. This means that instead of providing instructions on how to build your infrastructure, applying the relevant configuration, and deploying your application, you declare the end state of what you need. This means that your Git repository always maintains a single source of truth. As declarative changes are idempotent, you don’t need to worry about the state of your system as this will eventually become consistent with the code in Git.
- It versions desired system state using Git: As Git forms an excellent version control system, you don’t need to worry too much about how to roll out and roll back your deployments. A simple Git commit means a new deployment, and a Git revert means a rollback. This means you do not need to worry about anything apart from ensuring that the Git repository reflects...
