Chapter 10: Verified GitOps Setup – Continuous Delivery GitOps with Harness
When considering any kind of automation, understanding and mapping out the process is a hard requirement. Automation applied to an undefined process will result in gaps or holes that require manual intervention. Adopting a GitOps practice should start with documenting where automation is desired, how to define it in code, and how to trigger the execution.
The previous chapter walked through setting up originalist GitOps using Minikube, Helm, and ArgoCD. This chapter will look to set up verified GitOps, starting out with how to map the process and how to use declarative language for repeatability and reliability. Additionally, since an open source tool was used in the last chapter to show originalist GitOps, this chapter will use a vendor-based tool for verified GitOps.
In this chapter, we're going to cover the following main topics:
- Mapping out the process
- One manifest or many ...
