You're reading from Repeatability, Reliability, and Scalability through GitOps Continuous delivery and deployment codified

Product type Paperback

Published in May 2021

Publisher Packt

ISBN-13 9781801077798

Length 292 pages

Edition 1st Edition

Tools

GitOps

Concepts

Cloud Native

Author (1):

Bryan Feuling

View More author details

Table of Contents (17) Chapters

Preface

1. Section 1: Fundamentals of GitOps

2. Chapter 1: The Fundamentals of Delivery and Deployment FREE CHAPTER

3. Chapter 2: Exploring Common Industry Delivery and Deployment Practices

4. Chapter 3: The "What" and "Why" of GitOps

5. Section 2: GitOps Types, Benefits, and Drawbacks

6. Chapter 4: The Original GitOps – Continuous Deployment in Kubernetes

7. Chapter 5: The Purist GitOps – Continuous Deployment Everywhere

8. Chapter 6: Verified GitOps – Continuous Delivery Declaratively Defined

9. Chapter 7: Best Practices for Delivery, Deployment, and GitOps

10. Section 3: Hands-On Practical GitOps

11. Chapter 8: Practicing the Basics – Declarative Language File Building

12. Chapter 9: Originalist Gitops in Practice – Continuous Deployment

13. Chapter 10: Verified GitOps Setup – Continuous Delivery GitOps with Harness

14. Chapter 11: Pitfall Examples – Experiencing Issues with GitOps

15. Chapter 12: What's Next?

16. Other Books You May Enjoy

To push or pull ?

As the DevOps team considered the current versioning issue and updating the Kubernetes manifest files, they also wondered whether the GitOps tool should be inside or outside of a cluster.

Some of the benefits that the team came up with were things like direct cluster access. This was especially helpful with the monitoring and enforcement of Kubernetes resources. The tool would also have immediate knowledge of the health of the resources. Another benefit is that the execution engine should be fairly small with a low cost of ownership. Lastly, since the execution happens within the cluster, all data and secrets reside in the cluster as well. This would prevent the need for consistent polling for information from an external source.

There were also some benefits of having a GitOps execution engine live outside of the cluster. Most importantly, the execution engine is not dependent upon the life and health of the cluster. If the cluster, or the node that the execution...