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

The purpose of best practices

When the DevOps team first started out on the journey of automation, they were trying to script deployments to application servers. As the server pools and customer base grew, so did the need for more reliable deployment methods. These requirements changed rapidly as the company moved toward a cloud-native approach. The desire to adopt container-based and serverless applications with cloud infrastructure became the main drive behind the move for increased automation efforts. As the DevOps team built out a potential deployment solution for containers and Kubernetes, the directives once again shifted to include a broad range of platforms and architectures. Adding to the consistent scope of support shifting was a deadline that remained relatively consistent. This meant that the DevOps team had little time to document and plan, but rather had to implement a solution that was an inexpensive, high-quality product, and did so in a short period of time. And as...