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

Originalist GitOps with Argo CD

After the Git repository, the minikube cluster, and the Helm chart were set up, the DevOps team could now start working on getting the GitOps tools implemented. The first tool to test out for the team was Argo CD. Although Argo CD wasn't the first GitOps tool available, it was definitely the most popular tool. The goal of implementing Argo CD into the cluster was to show both how easily and quickly the solution can be set up and working, and how much work is required to make sure that Argo CD fits into their company's requirements.

Argo CD is open source, which is typically sought after by engineering teams because it is free. There are only a few commands that need to be run to get Argo CD working in a cluster. But the DevOps team would need to document how they would secure Argo CD against unauthorized use, how to leverage multiple clusters, how to bring on multiple Helm charts, and how to deploy across all environments sequentially with...