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

Mapping out the process

The DevOps team had already settled on two different potential solutions for applying GitOps practices to their delivery process. One of the tools, Ansible, is open source and allows the team to achieve their GitOps requirements without any licensing cost. The other tool, Harness, is not an open source tool and requires the company to purchase licenses. Harness also allows the team to achieve continuous delivery with GitOps, and with significantly less setup, configuration, and administration than Ansible.

As the deliberation over whether Harness will be purchased or not continues, the DevOps team is finding that they have less and less time to get their first iteration of the process ready and usable by the other engineers. To make the solution setup and configuration easier, they decide to map out their process, tools, platforms, security requirements, and so on. They know that a cloud platform and their data centers will all need to be supported. The artifacts...