This article is an English translation of my article posted on Japan’s most famous IT news site ITmedia on October 18, 2019, translated with the permission of ITmedia. https://www.atmarkit.co.jp/ait/articles/1910/21/news003.html
On July 9th, 2019, there was a historic announcement that IBM had completed its acquisition of Red Hat. On August 1st, just 3 weeks after this announcement, IBM announced that it would be renewing its software portfolio to be more cloud-native and optimized (and further optimized) to run on Red Hat OpenShift.
This new cloud-native product family is known as IBM Cloud Paks and it containerizes and packages IBM’s Middleware in order to support OpenShift. These facts show that IBM is focusing on simplifying the way that companies can update their applications to the latest versions and in particular, the migration to the cloud for mission-critical systems which have previously been a barrier to cloud migration.
Red Hat OpenShift, which has become IBM’s main container platform was originally flexibly designed to operate on-premises as well as on public or private clouds. Therefore, once an enterprise builds an application on OpenShift, that application can be run on any environment that can run OpenShift, such as all major public clouds (AWS, Microsoft Azure, Google Cloud etc.) as well as private clouds and on-premises.
On this occasion, using IBM Cloud’s OpenShift managed service “Red Hat OpenShift on IBM Cloud” which was both announced and started service on August 1st, I evaluated the multi-zone clusters that are using the three data centers located in the Tokyo region (TOK2, TOK04 and TOK05).
IBM considers integrated services with Red Hat to be of the upmost importance now and evaluating this is a most exciting and interesting experience that I want to share with everyone.
As an aside, Red Hat OpenShift on IBM Cloud was originally included in the service group that can be used with the Kubernetes managed service “IBM Cloud Kubernetes Service (IKS)”. In the case that a Kubernetes native environment is needed, a Kubernetes cluster can be configured and if an OpenShift environment is needed, an OpenShift cluster can be configured, so it’s convenient to use the different clusters as needed.
What are Multi-zone Clusters?
This refers to a configuration where worker nodes for an OpenShift Cluster are placed in multiple data centers. This ensures that even if there is a failure at a data center level, the impact on systems is kept to a minimum. Worker nodes are managed on the IBM Cloud side and the user can specify the fault tolerance of the worker nodes.
Creating OpenShift Clusters
I will explain the process to create OpenShift clusters.
Log in to the IBM Cloud Portal and from the dashboard screen, go to “Catalog” and then “Container” and click “Red Hat OpenShift Cluster”.
The “Red Hat OpenShift Cluster” service explanation will be displayed. Click “Create” and proceed.
The “Create a New OpenShift Cluster” screen will be displayed.