1 Why GitOps?

 

This chapter covers:

  • What is GitOps
  • Why GitOps is important
  • Comparison of GitOps with other approaches
  • Benefits of GitOps

1.1       Introduction

Kubernetes is an open-source platform that orchestrates and automates container operations. It eliminates many of the manual processes involved in deploying and scaling containerized applications. Git, initially developed by Linus Torvalds, the creator of Linux, is the most widely used version control system in the software industry today[1]. GitOps is a new method of Continuous Deployment that uses Git as a single source of truth for declarative infrastructure and applications, providing both revision and change control. With GitOps, a system is operated by the submission of pull requests (and subsequent merges) to the desired state of the system represented in a Git repository.

Using GitOps with Kubernetes, with its declarative style of configuration and active reconciliation model, provides the next level of infrastructure-as-code and immutable infrastructure through declarative continuous delivery systems, extends these core benefits to the deployment, monitoring, and lifecycle management of Kubernetes applications.

1.1.1   Who this book is for

1.1.2   Who this book is not for

1.1.3   How to use this book

1.2       Evolution to GitOps

1.2.1   Traditional Ops

1.2.2   DevOps

1.2.3   GitOps

1.3       Developer Benefits of GitOps

1.3.1   Infrastructure as Code

1.3.2   Self-Service

1.3.3   Code Reviews

1.3.4   Git Pull Requests

1.4       Operational Benefits of GitOps

1.4.1   Declarative

1.4.2   Observability

1.4.3   Disaster Recovery

1.4.4   Rollback

1.5       Summary

sitemap