Configure the OpenShift Cloud Provider

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

This document describes how to configure OpenShift for YugabyteDB universes using Yugabyte Platform. If no cloud providers are configured via the Yugabyte Platform console, the main Dashboard page requests to configure at least one provider, as per the following illustration:

To create a YugabyteDB universe using the deployed platform, you start by creating the required Role-based access control (RBAC) and adding the provider in the platform.

Creating RBAC and kubeconfig

kubeconfig is used by Yugabyte Platform to create universes in the OCP cluster.

To create a ServiceAccount in the yb-platform project, execute the following command:

Expect the following output:

serviceaccount/yugabyte-platform-universe-management created

The next step is to grant access to this ServiceAccount using Roles and RoleBindings, thus allowing it to manage the YugabyteDB universe's resources for you. To create the required RBAC objects, execute the following command:

Expect the following output:

role.rbac.authorization.k8s.io/yugabyte-helm-operations created
role.rbac.authorization.k8s.io/yugabyte-management created
rolebinding.rbac.authorization.k8s.io/yugabyte-helm-operations created
rolebinding.rbac.authorization.k8s.io/yugabyte-management created

The next step is to create a kubeconfig for this ServiceAccount. You download a helper script for generating a kubeconfig file by executing the following command:

To generate the kubeconfig file, execute the following:

Expect the following output:

Generated the kubeconfig file: /tmp/yugabyte-platform-universe-management.conf

Creating a Provider in Yugabyte Platform

Since Yugabyte Platform manages YugabyteDB universes, Yugabyte Platform needs details about the cloud providers. In your case, the provider is your own OCP cluster.

You can create a provider as follows:

• Open the Yugabyte Platform web UI and click Configure a Provider to open the Cloud Provider Configuration page shown in the following illustration.

• Select Red Hat OpenShift and complete the fields, as follows:

  • In the Type filed, select OpenShift.
  • In the Name field, enter ocp-test.
  • Use the Kube Config field to select the file that you created in the preceding step.
  • In the Service Account field, enter yugabyte-platform-universe-management.
  • In the Image Registry field, if you are performing Operator-based installation, use registry.connect.redhat.com/yugabytedb/yugabyte, and if you are performing Helm-based installation, use quay.io/yugabyte/yugabyte-ubi
  • Optionally, use the Pull Secret File field to upload the pull secret you received from Yugabyte Support.
    
    

• Click Add Region and complete the Add new region dialog shown in the following illustration by first selecting the region you found previously (US East), and then entering the following information:

  • In the Zone field, enter the exact zone label (us-east4-a).
  • In the Namespace field, enter yb-platform.
    
    

  

• Click Add Region.

• Click Save.

You should see the newly-added provider under Red Hat OpenShift configs.

Creating a Universe Using the Provider

You can create a universe using the provider as follows:

• Use the Yugabyte Platform web UI to navigate to Universes and then click Create Universe.

• Complete the Create Universe page shown in the following illustration by entering the following information:

  • In the Name field, enter universe-1.
  • In the Provider field, enter ocp-test.
  • In the Regions field, enter US East.
  • In the Instance Type field, enter xsmall (2 cores, 4GB RAM).
    
    

  

• Click Create.

The following illustration shows the universe creation progress:

If you click universe-1 and then navigate to Tasks, you should see a page similar to the one shown in the following illustration:

Upon successful creation of the universe, the Overview tab of universe-1 should look similar to the following:

Troubleshooting the Universe Creation

If the universe creation remains in Pending state for more than 2-3 minutes, open the OCP web console, navigate to Workloads > Pods and check if any of the pods are in pending state, as shown in the following illustration:

Alternatively, you can execute the following command to check status of the pods:

Expect the following output:

# output
NAME          READY STATUS  RESTARTS AGE
yb-master-0   2/2   Running  0     5m58s
yb-master-1   2/2   Running  0     5m58s
yb-master-2   0/2   Pending  0     5m58s
yb-tserver-0  2/2   Running  0     5m58s
yb-tserver-1  2/2   Running  0     5m58s
yb-tserver-2  2/2   Running  0     5m58s

If any of the pods are in pending state, perform the following:

• Login with an admin account and navigate to Compute > Machine Sets.
• Open the Machine Set corresponding to your zone label (us-east4-a).
• Click Desired Count and increase the count by 1 or 2, as shown in the following illustration.
• Click Save.

Alternatively, you can scale the MachineSets by executing the following command as admin user:

Expect the following output:

# output
machineset.machine.openshift.io/ocp-dev4-l5ffp-worker-a scaled

As soon as the new machine is added, the pending pods become ready.