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

One manifest or many

The DevOps team had completed the process mapping and understood what was required for the delivery of each application type. They gathered information related to the tools, the platforms, the permissions and access requirements for the tools and platforms, and the teams that are concerned with each phase. If the engineering leadership decides to move forward with Ansible, then the DevOps team will need to convert the process map into the declarative file structure that Ansible expects. However, if the decision is to move forward with Harness, then the DevOps team will only have to build out the process map in Harness, which has its own automated file generation process on the backend.

Since the conversion of the process map to Ansible would be the most time-consuming process, the DevOps team decided to start building out the required Ansible playbooks. But, before they could start building those playbooks out, they had to decide on how the files would be structured...