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

Needs versus wants

It wasn't until the second proof-of-concept for these tools that the teams started to get more attention from the business leadership. The CDO was curious to see what the DevOps team was doing, especially if there were measurable effects of the recent DevOps initiatives. The DevOps team was able to share what requirements had been gathered, what tools were being evaluated, and so on. For some, the speed at which these steps were accomplished were extremely fast. But the CDO was not as impressed with the timeline.

The initial directive and timeline, which was the main driver for all of the work the DevOps team had done, was now being altered. The CDO needed the teams to have a beta version of the application deploying to Kubernetes within a month.

The DevOps team immediately went into panic mode. Although the developers would be able to get the artifacts ready in time, the delivery pipeline would not be. The amount of time available meant that the DevOps...