Why IBM Cloud is THE Cloud to Run OpenShift 4.3

2 min read

OpenShift 4.3 is now generally available.

We are excited to announce support of OpenShift 4.3 in the managed OpenShift offering. IBM provides the most secure managed OpenShift offering through a jointly developed project, Hypershift Toolkit, to ensure that users have access to the cluster-admin role to run those privileged workloads while IBM provides guardrails around the master nodes to ensure the customer cannot break the cluster. 

What is Red Hat OpenShift on IBM Cloud?

Red Hat OpenShift on IBM Cloud launched August 1, 2019, and is a managed service that simplifies deployment and configuration of the OpenShift Container Platform. As a managed service, IBM will automate initial provisioning as well as on-going maintenance, including operating system patches, vulnerability remediation, and any updates in the OpenShift stack. 

Lifecycle management is only one aspect of a managed OpenShift offering, however. Another key aspect is building in operational efficiencies so you can deliver line-of-business objectives. We do that by supporting highly available (HA) master nodes in a multizone cluster configuration. This ensures that master and worker nodes are distributed evenly across at least three physically separate data centers (i.e., zones) within that region. 

Managed OpenShift supports your most critical workloads by providing an SLA of 99.99% on a variety of compute isolation choices, including bare metal. Managed OpenShift also supports your regulated workloads with compliance, including PCI, HIPAA-ready, ISO, SOC 1, and SOC 2 Type 1 and Type 2. 

How to deploy an OpenShift cluster

Demo video overview:

Step-by-step guide:

  1. Log in to IBM Cloud.
  2. Navigate to the Catalog > Services > Containers section and select Red Hat OpenShift on IBM Cloud.
    Navigate to the Catalog > Services > Containers section and select Red Hat OpenShift on IBM Cloud.
  3. Select the version of OpenShift (here, of course, we want to try the latest 4.3 version).
  4. Provide a name for the cluster. Optionally, you can select a resource group to associate this cluster with and add a tag to help you identify that cluster later.
    Provide a name for the cluster. Optionally, you can select a resource group to associate this cluster with and add a tag to help you identify that cluster later.
  5. Under Location, we will use the Multizone option to take advantage of HA masters and workers running in those three separate data centers.
    5.	Under Location, we will use the Multizone option to take advantage of HA masters and workers running in those three separate data centers.
  6. Next, we will create the default worker pool. You can select a variety of compute isolation, including bare metal. After the cluster is deployed, you can always create a new worker pool with a different sized worker.
    6.	Next, we will create the default worker pool. You can select a variety of compute isolation, including bare metal. After the cluster is deployed, you can always create a new worker pool with a different sized worker.
  7. At the bottom, you can specify the number of nodes in each data center (zone) and then click Create.
    At the bottom, you can specify the number of nodes in each data center (zone) and then click Create.
  8. Once the cluster is fully deployed, you can manage it from the UI or CLI.
    Once the cluster is fully deployed, you can manage it from the UI or CLI.
  9. Now you have full access to the OpenShift user experience, including OperatorHub.
    Now you have full access to the OpenShift user experience, including OperatorHub.

Join the discussion

If you have questions or concerns, engage our team via Slack. You can register here and join the discussion in the #general channel on https://ibm-cloud-success.slack.com/.

Be the first to hear about news, product updates, and innovation from IBM Cloud