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
OpenShift Multi-Cluster Management Handbook

You're reading from   OpenShift Multi-Cluster Management Handbook Go from architecture to pipelines using GitOps

Arrow left icon
Product type Paperback
Published in Nov 2022
Publisher Packt
ISBN-13 9781803235288
Length 458 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Authors (2):
Arrow left icon
Rafael Pecora Rafael Pecora
Author Profile Icon Rafael Pecora
Rafael Pecora
Giovanni Fontana Giovanni Fontana
Author Profile Icon Giovanni Fontana
Giovanni Fontana
Arrow right icon
View More author details
Toc

Table of Contents (23) Chapters Close

Preface 1. Part 1 – Design Architectures for Red Hat OpenShift
2. Chapter 1: Hybrid Cloud Journey and Strategies FREE CHAPTER 3. Chapter 2: Architecture Overview and Definitions 4. Chapter 3: Multi-Tenant Considerations 5. Chapter 4: OpenShift Personas and Skillsets 6. Part 2 – Leverage Enterprise Products with Red Hat OpenShift
7. Chapter 5: OpenShift Deployment 8. Chapter 6: OpenShift Troubleshooting, Performance, and Best Practices 9. Chapter 7: OpenShift Network 10. Chapter 8: OpenShift Security 11. Part 3 – Multi-Cluster CI/CD on OpenShift Using GitOps
12. Chapter 9: OpenShift Pipelines – Tekton 13. Chapter 10: OpenShift GitOps – Argo CD 14. Chapter 11: OpenShift Multi-Cluster GitOps and Management 15. Part 4 – A Taste of Multi-Cluster Implementation and Security Compliance
16. Chapter 12: OpenShift Multi-Cluster Security 17. Chapter 13: OpenShift Plus – a Multi-Cluster Enterprise Ready Solution 18. Chapter 14: Building a Cloud-Native Use Case on a Hybrid Cloud Environment 19. Part 5 – Continuous Learning
20. Chapter 15: What’s Next 21. Index 22. Other Books You May Enjoy

What is GitOps?

The term GitOps was first described by Lexis Richardson, CEO of Weaveworks, in 2017. At that time, he presented the four principles of GitOps, which are as follows:

  • The entire system is described declaratively: This means that any configuration of your application and infrastructure needs to be treated as code, but not as a set of instructions, as you would with scripts or automation code. Instead, you must use a set of facts that describes the desired state of your system. These declaration files are versioned in Git, which is your single source of truth. The great benefit of this principle is that you can easily deploy or roll back your applications and, more importantly, restore your environment quickly if a disaster occurs.
  • The canonical desired system state is versioned in Git: Git is your source of truth. It needs to be the single place that triggers all the changes in your systems. Ideally, nothing should be done directly on the systems, but through...
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