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)
1
Section 1: Fundamentals of GitOps
5
Section 2: GitOps Types, Benefits, and Drawbacks
10
Section 3: Hands-On Practical GitOps

A manifest for delivery

As the DevOps team is building out the workflows for the delivery pipeline, they are trying to take into consideration the wide array of functionality that needs support. Although the basic platform deployments are easy to define and build, there are other teams that need to execute their process requirements as well. The cloud team wants to run their Terraform processes through deployment workflows, but they also want to provide some level of self-service Terraform executions for the developers as well. The quality team has different tests that need to be run as a part of the deployments. Security scans need to be run on the artifact before the deployment is executed, but only on the lowest non-production environment. And the auditing and compliance group requires that tickets are created and updated throughout the delivery, as well as having an approval gate before a deployment executes against production.

The DevOps team can add some of the peripheral...