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

Verified GitOps basics

The past few months of developing and implementing GitOps tools and processes have been illuminating for the DevOps team. The changes in scope from the business and engineering leadership were somewhat discouraging. However, as the team had to restart their efforts when implementing GitOps, they realized that the new requirements helped with futureproofing. Each process or tool that the team had looked at seemed like a great solution for the requirements at that time. But as they tested the solutions, especially with each scope change, they quickly realized that the inevitable future requirements would not have been met. Requirements such as cross-platform support, cloud-native and traditional support, and a desire for repeatable, reliable, and scalable processes were difficult to achieve with the other tools.

These requirements lead them to Ansible, which seemed like it was going to offer the best option for leveraging GitOps across all platform types. One...