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

Common verified GitOps tools

The process of designing the requirements for verified GitOps gave the team a better understanding of where they should spend their time. The DevOps team has experienced building an in-house solution before, mainly avoid the costs of buying a tool. But they have also experienced the significant administration and maintenance effort associated to building a tool. Although Ansible had offered a wide range of customization capabilities, it was essentially a tool that they would have to build out and maintain. The other problem with Ansible was that although the files could be stored in a Git repository and pulled at runtime, the tool required the Git repository to be pulled down before every execution.

After performing market research for a verified GitOps tool, the team found Harness, which had a very promising solution. The tool allowed the team to support Kubernetes, serverless, and server-based platforms. It had a native code conversion process that...