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

Summary

Verified GitOps is a practice that leverages declarative language files to solve the automation around the delivery process. By codifying the integrations, permissions, and executions, the team that adopts verified GitOps can quickly ensure it is repeatable, reliable, and scalable for every delivery. But since there are no tools that are purpose-built for verified GitOps, the options are limited to either a delivery-based tool, such as Harness, or a general script-running tool, such as Ansible.

In the next chapter, we will cover the best practices for deployment, delivery, and GitOps. The adoption of best practices will not only result in meeting industry standards, but also allow for a team and company to avoid tool lock-in.