Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Repeatability, Reliability, and Scalability through GitOps

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

Arrow left icon
Product type Paperback
Published in May 2021
Publisher Packt
ISBN-13 9781801077798
Length 292 pages
Edition 1st Edition
Tools
Arrow right icon
Author (1):
Arrow left icon
Bryan Feuling Bryan Feuling
Author Profile Icon Bryan Feuling
Bryan Feuling
Arrow right icon
View More author details
Toc

Table of Contents (17) Chapters Close

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

Test, governance, deploy, verify, and restore as code

When the DevOps team was documenting the different stages of their desired delivery pipeline design, they wanted to include significantly more than just the deployment process. There was a desire to include QA testing, change management, verification of the production environment, and failure remediation. But shortly after those original design meetings, the team experienced an accelerated timeline and scope change. If they wanted to revisit the idea of automating the delivery process, especially with verified GitOps, they would need internal support.

The team found that it was better to start with a specific platform, build out the delivery pipeline for that platform, and then expand to the other platform support afterward. And because of the native execution capabilities of Kubernetes, it would be less of a lift for the team to build out the delivery pipeline for the containerized applications.

Initially, the team would...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at €18.99/month. Cancel anytime