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

A manifest for configuration

The next set of manifests that the DevOps team would need to create relate to the configuration requirements for the different platforms that need to be supported. The current platform support requirements are traditional Linux servers, Kubernetes clusters, and serverless functions in a cloud provider. Each of these platforms has specific configuration requirements, mainly related to networking and scaling. The traditional server platform would require a configuration file to exist on the server, while also updating any application server requirements. The Kubernetes platform would require updates related to any support tools that live in the cluster, as well as any ConfigMap or Secrets updates that might be required. In regard to the serverless function support, any configuration change will be associated with the deployment of the new function version.

The first issue that the DevOps team encountered was that the changes to the server-based applications...