Book Image

OpenShift Multi-Cluster Management Handbook

By : Giovanni Fontana, Rafael Pecora
5 (1)
Book Image

OpenShift Multi-Cluster Management Handbook

5 (1)
By: Giovanni Fontana, Rafael Pecora

Overview of this book

For IT professionals working with Red Hat OpenShift Container Platform, the key to maximizing efficiency is understanding the powerful and resilient options to maintain the software development platform with minimal effort. OpenShift Multi-Cluster Management Handbook is a deep dive into the technology, containing knowledge essential for anyone who wants to work with OpenShift. This book starts by covering the architectural concepts and definitions necessary for deploying OpenShift clusters. It then takes you through designing Red Hat OpenShift for hybrid and multi-cloud infrastructure, showing you different approaches for multiple environments (from on-premises to cloud providers). As you advance, you’ll learn container security strategies to protect pipelines, data, and infrastructure on each layer. You’ll also discover tips for critical decision making once you understand the importance of designing a comprehensive project considering all aspects of an architecture that will allow the solution to scale as your application requires. By the end of this OpenShift book, you’ll know how to design a comprehensive Red Hat OpenShift cluster architecture, deploy it, and effectively manage your enterprise-grade clusters and other critical components using tools in OpenShift Plus.
Table of Contents (23 chapters)
1
Part 1 – Design Architectures for Red Hat OpenShift
6
Part 2 – Leverage Enterprise Products with Red Hat OpenShift
11
Part 3 – Multi-Cluster CI/CD on OpenShift Using GitOps
15
Part 4 – A Taste of Multi-Cluster Implementation and Security Compliance
19
Part 5 – Continuous Learning

Argo CD definitions and challenges

Before we walk through the application deployment process, we need to discuss some important challenges related to GitOps, decisions, and standards.

GitHub repository structure

The first important question that always comes up with GitOps is about the GitHub repository’s structure. Should I only use one repository for source code and the Kubernetes manifests? How should I deal with different configuration files for different environments, such as development, QA, and production?

Well, there are no right or wrong answers to these questions, as each option has its pros and cons. You need to find out which approach works best for you. My advice here is: try it! There is nothing better than practical experience, so use each model and find out which one fits best for your applications and teams. In the following sections, we’ll look at some of the most popular repository structures out there for GitOps-oriented applications.

Mono...