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

OpenShift Plus – a practical use case

Let’s consider the following use case. Try to use the concepts we covered in this book to identify which tool you could use to cover each requirement.

Use case: The company HybridMyCloud is developing an AI/ML application that has the following requirements:

  • The application life cycle is comprised of Development, QA, Pre-prod, and Production environments.
  • Development and QA can share the same underlying platform. Pre-prod and Production need to be separated due to regulatory needs. Production application needs to be in a private subnet, with no public direct access from the internet.
  • The C-level and procurement department of HybridMyCloud signed a contract with AWS and, due to that, wants to host most resources there. However, they don’t want to be locked into it and want to have the ability to move the application to Azure when needed.
  • This AI/ML application is based on containers and stateless, however...