Book Image

Repeatability, Reliability, and Scalability through GitOps

By : Bryan Feuling
Book Image

Repeatability, Reliability, and Scalability through GitOps

By: Bryan Feuling

Overview of this book

The world of software delivery and deployment has come a long way in the last few decades. From waterfall methods to Agile practices, every company that develops its own software has to overcome various challenges in delivery and deployment to meet customer and market demands. This book will guide you through common industry practices for software delivery and deployment. Throughout the book, you'll follow the journey of a DevOps team that matures their software release process from quarterly deployments to continuous delivery using GitOps. With the help of hands-on tutorials, projects, and self-assessment questions, you'll build your knowledge of GitOps basics, different types of GitOps practices, and how to decide which GitOps practice is the best for your company. As you progress, you'll cover everything from building declarative language files to the pitfalls in performing continuous deployment with GitOps. By the end of this book, you'll be well-versed with the fundamentals of delivery and deployment, the different schools of GitOps, and how to best leverage GitOps in your teams.
Table of Contents (17 chapters)
Section 1: Fundamentals of GitOps
Section 2: GitOps Types, Benefits, and Drawbacks
Section 3: Hands-On Practical GitOps

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
  • ...