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

Building and testing Kubernetes manifests

With the DevOps team finishing out the migration of their Kubernetes applications in Harness, the business is starting to see significant improvements in the stability of their products. The next application for the DevOps team to add to Harness is the serverless application, and then the traditional applications last. Although the immediate requirements are to support the traditional applications alongside the cloud-native applications, there has been talk about the potential of decomposing the traditional applications into cloud-native structures.

For the traditional applications to move over to a cloud-native architecture, the teams will need to learn how to decompose, or slowly break down, the traditional applications into container-based functionality. The DevOps team will have to provide a set of documented best practices on how to get a container onto Kubernetes using Helm Charts. That will require that the developers not only have...