IBM Cloud Docs
Ordering Red Hat OpenShift for VMware

Ordering Red Hat OpenShift for VMware

You can include the Red Hat® OpenShift® for VMware® service with a new VMware Cloud Foundation for Classic - Automated instance or add the service to your existing instance.

Considerations when you install Red Hat OpenShift for VMware

  • Before the service is installed in your environment, a check is completed against the available capacity of the target cluster in the environment to ensure that the service components can fit. The storage capacity check applies only to vSAN storage. For NFS clusters, a new NFS data store, dedicated to Red Hat OpenShift, is added.
  • The cluster is associated with the Red Hat account from the pull secret that is provided.
  • The Latency Sensitivity setting of the Red Hat OpenShift cluster VMs can affect the Kubernetes scheduling performance. This value is preset to Normal, but you can change it to High if you encounter Kubernetes performance issues.

Ordering Red Hat OpenShift for VMware for a new instance

  1. When you order the instance, scroll down to the Add-on services section. Red Hat OpenShift for VMware is in the Transformation and modernization of VMware applications category.
  2. Open the category, locate Red Hat OpenShift for VMware, and toggle its switch on.
  3. Click Edit to review and specify the configuration information, then click Save.

Ordering Red Hat OpenShift for VMware for an existing instance

  1. On the instance details page, click the Services tab.
  2. Click Add to add the service.
  3. On the Add services page, locate the Red Hat OpenShift for VMware service in the Transformation and modernization of VMware applications section and toggle its switch on.
  4. Click Edit to review and specify the configuration information, then click Save.

Red Hat OpenShift for VMware configuration

When you order the service, you must provide a Red Hat® pull secret. This pull secret is used to associate the new Red Hat OpenShift cluster with your existing Red Hat account. You can obtain a copy of your pull secret by logging in to your Red Hat account and clicking Copy Pull Secret.

Setting up DNS to access your Red Hat OpenShift console

Red Hat OpenShift depends on DNS to function properly. The ocp wildcard zone in your VMware environment root zone resolves all names to the IP address of the Red Hat OpenShift cluster application. This way, all applications that run within Red Hat OpenShift are routed through the Load Balancer, as needed.

Because the Red Hat OpenShift web console runs as an application within Red Hat OpenShift, your system must properly resolve DNS names before you can connect to the Red Hat OpenShift web console. You must complete the following steps before you open the Red Hat OpenShift console:

  1. Ensure that you are connected to your environment by using the IBM Cloud infrastructure VPN.
  2. Ensure that the system used to connect to the Red Hat OpenShift web console can properly resolve hostnames in the DNS zone for your VMware environment. For an existing DNS infrastructure, configure the DNS delegation. Therefore, the queries for hostnames within the VMware instance's root zone are handled by the AD DNS server that is running within your VMware environment.

Alternately, you can configure your local hosts file with the following entries so you can access the Red Hat OpenShift web console. Use the following example:

APPLICATION_IP  console-openshift-console.apps.ocp.ROOTDOMAIN

APPLICATION_IP oauth-openshift.apps.ocp.ROOTDOMAIN

In the previous example:

  • Replace APPLICATION_IP with the Red Hat OpenShift application IP address shown in the Red Hat OpenShift service details page.
  • Replace ROOTDOMAIN with the root domain shown on the Summary page for the VCF for Classic - Automated instance.