Chapter 6: Verified GitOps – Continuous Delivery Declaratively Defined
The last GitOps concept that we will cover is a relatively recent practice known as verified GitOps. The essential difference between verified GitOps and the other GitOps practices is the desire to leverage GitOps for the entirety of continuous delivery, rather than only for continuous deployment.
One operating requirement across all GitOps practices is the need for declarative language files to be stored in a source code manager and referenced at runtime. And, depending on which practice is being adopted, the number of required files is heavily impacted based on the desired manual intervention. This results in a balancing act between manual intervention steps and the number of declarative files.
In this chapter, we're going to cover the following main topics:
- Verified GitOps basics
- Test, governance, deploy, verify, and restore as code
- One file, many files, or somewhere...
