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

One file, many files, or somewhere in-between

The DevOps team was finishing the design work on a verified GitOps pipeline and began documenting the requirements for the different integrations. They figured that they would need a set of declarative files for every integration, which included access and execution requirements. Then, they would be able to reuse those files in any pipelines that needed them. Because every provider, platform, and tool required these different sets of filesthe team would need to figure out the best folder hierarchy to store the files.

The team would then need to build out a set of declarative files that defined the required variables for integration interactions. Each interaction definition file would have to reference the appropriate integration files for access and permission requirements.

Next, the team would need to build some environment-specific execution requirements to enforce security and compliance standards for every deployment. The DevOps...