GCP
Add an Ingress Controller to an OSD GCP Cluster and optionally with a custom domain.
Starting with OpenShift 4.14, OSD GCP supports adding additional Ingress Controllers which can use used to configure a custom domain on a OSD GCP cluster without having to use the now deprecated Custom Domain Operator. This guide shows how to add an additional Ingress Controller ( public or private ) to a OSD GCP cluster and optionally also configuring a custom domain.
Prerequisites
- A Red Hat OpenShift Dedicated on GCP (OSD GCP) cluster, version 4.14 or above
- The oc CLI #logged in.
Set up environment
- Export few environment variables
Important: The variables below can be customized to fit your needs for your ingress controller.
Limit Egress with Google Secure Web Proxy
In this guide, we will implement egress restrictions for OpenShift Dedicated by using Google’s Secure Web Proxy . Secure Web Proxy is a cloud first service that helps you secure egress web traffic (HTTP/S). OpenShift Dedicated relies on egress being allowed to specific fully qualified domain names (FQDNs), not just IP addresses. Secure Web Proxy provides support for limiting egress web traffic to the FQDNs necessary for the external endpoints that OpenShift Dedicated relies on.
Maximo Application Suite on OpenShift Dedicated Google Cloud Platform ( OSD GCP )
IBM Maximo Application Suite (MAS) is a set of applications for asset monitoring, management, predictive maintenance and reliability planning. When combined with Red Hat OpenShift Dedicated on Google Cloud ( OSD GCP ), this frees up your Maximo and operations team to focus on what is important to them ( Maximo ) rather than having to worry about managing and building clusters.
This document outlines how to get quickly get started with OSD GCP and installing Maximo all through automation.
Limit Egress with Google Cloud NGFW Standard
In this guide, we will implement egress restrictions for OpenShift Dedicated by using Google’s Cloud Next Generation Firewall (NGFW) Standard . Cloud NGFW is a fully distributed firewall service that allows fully qualified domain name (FQDN) objects in firewall policy rules. This is necessary for many of the external endpoints that OpenShift Dedicated relies on.
OSD on Google Cloud
Creating a OSD in GCP with Existing VPCs
Tip The official documentation for installing a OSD cluster in GCP can be found here .
For deploy an OSD cluster in GCP using existing Virtual Private Cloud (VPC) you need to implement some prerequisites that you must create before starting the OpenShift Dedicated installation though the OCM.
Prerequisites
NOTE: Also the GCloud Shell can be used, and have the gcloud cli among other tools preinstalled.
Create Filestore Storage for OSD in GCP
By default, within OSD in GCP only the GCE-PD StorageClass is available in the cluster. With this StorageClass, only ReadWriteOnce mode is permitted, and the gcePersistentDisks can only be mounted by a single consumer in read-write mode .
