We’re excited to announce that IBM Cloud Kubernetes Service and Red Hat OpenShift on IBM Cloud are now both generally available in the new Toronto Multizone Region.

Data sovereignty is the premise that the data an organization collects, stores and processes is subject to that nation’s data privacy regulations, guidelines and best practices. IBM Cloud enables enterprises to host their data in the Canadian data centers, meeting the strict data residency and sovereignty requirements.

IBM Cloud Kubernetes Service and Red Hat OpenShift on IBM Cloud are now GA

IBM Cloud Kubernetes Service and Red Hat OpenShift on IBM Cloud are both generally available in the new Toronto MZR (Multizone Region), enabling our customers to run these workloads and ensuring all data remains within the Canadian boundaries.

The IBM Cloud Kubernetes Service and Red Hat OpenShift on IBM Cloud are both fully managed offerings that deliver powerful management tools, an intuitive user experience and built-in security and isolation to enable rapid delivery of applications — all while leveraging Cloud Services like cognitive capabilities from IBM Watson.

The offerings provide native Kubernetes capabilities like intelligent scheduling, self-healing, horizontal scaling, service discovery and load balancing, automated rollouts/rollbacks and secret and configuration management. IBM is also adding capabilities to the services, including simplified cluster management, container security and isolation choices, the ability to design your own cluster and leverage other IBM Cloud services (such as Watson) for your cognitive applications, completely native Kubernetes CLI and API and integrated operational tools:

Deploying clusters in the Canadian MZR

1. Create your VPC in the Toronto MZR using the Getting started with VPC guide.
2. In the Catalog, locate the Kubernetes Service or Red Hat OpenShift on IBM Cloud tile to deploy a new cluster:

3. Select the Red Hat OpenShift on IBM Cloud offering. on the cluster details page, select the desired OpenShift version, then VPC as the infrastructure. Now choose the VPC created in Step 1:

4. Change the flavor type and quantity in the default worker pool, provide a unique name if necessary, master service endpoint connectivity, cluster name and click the Create button:

5. Upon successful deployment, you can view the cluster details:

Congratulations, you are now running a Kubernetes or OpenShift cluster with master nodes and worker nodes fully within the Toronto MZR — solving your Canadian data sovereignty concerns.

Join the conversation

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/.