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 11: Pitfall Examples – Experiencing Issues with GitOps

A major section of this book was dedicated to covering the high-level understanding of different GitOps practices, how they are implemented, as well as benefits and drawbacks. This chapter is intended to show some of the drawbacks of GitOps in a more practical way.

To follow along with this chapter, you will need to follow the steps in Chapter 9, Originalist Gitops in Practice – Continuous Deployment, related to getting minikube, a Git repository, and Argo CD set up and running. The assumption throughout this chapter is that the user has Argo CD running in the minikube cluster and Argo CD connected to a Git repository. Although Argo CD is the main tool used for this chapter, that is only because Argo CD is the lightest and quickest to get set up and show pitfalls. This chapter is not intended to show issues with Argo CD, but rather pitfalls that can accompany GitOps in general.

In this chapter, we&apos...