Prepare the OpenShift environment

• AWS
• GCP
•    Azure
• Kubernetes
• OpenShift
• On-premises

To prepare the environment for OpenShift, you start by provisioning the OpenShift cluster.

The recommended OpenShift Container Platform (OCP) version is 4.6, with backward compatibility assumed but not guaranteed.

You should have 18 vCPU and 32 GB of memory available for testing Yugabyte Platform. This can be three or more nodes equivalent to Google Platform's n1-standard-8 (8 vCPU, 30 GB memory).

For more information and examples on provisioning OpenShift clusters on GCP, see the following:

• Configuring a GCP project
• Installing a cluster quickly on GCP

In addition, ensure that you have the following:

• The latest oc binary in your path. For more information, see Installing the OpenShift CLI.
• The latest kubectl 1.19.7 binary in your path. See Install and Set Up kubectl for more information, or create a kubectl symlink pointing to oc.
• An admin user¹ with the cluster-admin ClusterRole bound to it. Depending on your configuration, this user might be kube:admin.
• An authenticated user² in the cluster which can create new projects³.

For testing purposes, you may configure an HTPasswd provider, as described in Configuring an HTPasswd identity provider (specifically, in Creating an HTPasswd file using Linux and Configuring identity providers using the web console).

---

1. This user is referred to as admin user in this documentation. ↩︎

2. This user is referred to as normal user, non admin, or user in this documentation. ↩︎

3. By default, the authenticated users have the self-provisioning ClusterRole bound to them, which enables them to create new projects. ↩︎