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

Declarative files overload

Jenkins, Terraform, Kubernetes, Tomcat, servers, serverless, containers, pipelines, builds, and plugins. These are the tools, solutions, and architecture types that the DevOps team had to implement in a scalable, repeatable, and reliable way through GitOps. Implementing GitOps with just Kubernetes had its own issues but was significantly easier than trying to leverage a GitOps process for servers, serverless, and container architectures.

Initially, the team thought that by having the developers maintain a Jenkinsfile for every service repository, they would reduce the administration requirement for deployments. This was a rather easy setup when considering a traditional server-based infrastructure. The developers would simply add the desired configuration information that the application would need to their Jenkinsfile. Jenkins would then be able to pass the configuration requirements to the server at runtime, execute the restart and copy commands, and...