--- name: openshift-locations title: Understanding IBM Cloud locations and regions description: Learn how IBM Cloud locations and regions are organized for cluster deployments, including multizone regions and single-campus multizone regions. last-updated: 2026-08-03 --- > ## Documentation Index > The table of contents for this documentation set is at https://cloud.ibm.com/docs/openshift?format=markdown > The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt > Use these files to discover more information as needed. # Understanding IBM Cloud locations and regions {: #regions-and-zones} Learn how IBM Cloud locations and regions are organized for cluster deployments, including multizone regions and single-campus multizone regions. {: shortdesc} ## VPC multizone regions {: #zones-vpc} VPC resources are provisioned in a region, which is a separate group of zones within a metro. The zones are mapped to separate data centers to ensure that resources are distributed evenly across zones in a multizone architecture. In the API and CLI, zones use the regional zone name in the API and command line (`us-south-1`), but in the console, zones use by the data center location (`Dallas 1`). For the data center code that the VPC zone and location corresponds to, such as `us-south-1` and `DAL10`, see [Multizone regions](https://cloud.ibm.com/docs/overview?topic=overview-locations&format=markdown#table-mzr). {: shortdesc} Mumbai (`in-mum`) VPC MZR limitations : **Operating systems**: You can only create clusters at version 4.16 and later in Mumbai and can only use RHEL 9 or RHCOS workers nodes. : **Baremetal workers**: Baremetal VPC worker nodes are not available in Mumbai. Chennai (`in-che`) VPC MZR limitations : **Operating systems**: You can only create clusters at version 4.16 and later in Chennai and can only use RHEL 9 or RHCOS workers nodes. : **Baremetal workers**: Baremetal VPC worker nodes are not available in Chennai. Montreal (`ca-mon`) VPC MZR limitations : **Webhooks**: Only webhooks that access an in-cluster service work. Webhooks that directly access an external, out of cluster, URL are blocked. : **Operating systems**: You can only create clusters at version 4.16 and later in Montreal and can only use RHEL 9 or RHCOS workers nodes. : **Portworx Enterprise** and **Portworx Backup**: The default installation method for Portworx Enterprise and Portworx Backup is not yet supported for private-only clusters in the Montreal region. Contact Portworx Support if you need to install Portworx Enterprise or Portworx Backup in a private-only cluster in Montreal. For more information, see [Portworx Support](https://cloud.ibm.com/docs/openshift?topic=openshift-storage_portworx_about&format=markdown#portworx-billing-support). ![Red Hat OpenShift on IBM Cloud VPC multizone regions](images/locations-vpc.svg){: caption="Red Hat OpenShift on IBM Cloud locations" caption-side="bottom"} This image is an artistic representation and does not reflect actual political or geographic boundaries. {: note} | Geography | Country | Metro | Region | Zones | | --- | --- | --- | --- | --- | | Asia Pacific | Australia | Sydney | au-syd | au-syd-1, au-syd-2, au-syd-3 | | Asia Pacific | India | Chennai | in-che | in-che-1, in-che-2, in-che-3 | | Asia Pacific | India | Mumbai | in-mum | in-mum-1, in-mum-2, in-mum-3 | | Asia Pacific | Japan | Osaka | jp-osa | jp-osa-1, jp-osa-2, jp-osa-3 | | Asia Pacific | Japan | Tokyo | jp-tok | jp-tok-1, jp-tok-2, jp-tok-3 | | Europe | Germany | Frankfurt | eu-de | eu-de-1, eu-de-2, eu-de-3 | | Europe | Spain | Madrid | eu-es | eu-es-1, eu-es-2, eu-es-3 | | Europe | United Kingdom | London | eu-gb | eu-gb-1, eu-gb-2, eu-gb-3 | | North America | Canada | Montreal | ca-mon | ca-mon-1, ca-mon-2, ca-mon-3 | | North America | Canada | Toronto | ca-tor | ca-tor-1, ca-tor-2, ca-tor-3 | | North America | United States | Dallas | us-south | us-south-1, us-south-2, us-south-3 | | North America | United States | Washington DC | us-east | us-east-1, us-east-2, us-east-3 | | South America | Brazil | São Paulo | br-sao | br-sao-1, br-sao-2, br-sao-3 | {: caption="Available multizone regions for VPC clusters in Red Hat OpenShift on IBM Cloud." caption-side="bottom"} {: #vpc-gen2-multizone-locations-table} ## Classic regions {: #locations-classic} The term `zone` in this document refers to different things depending the type of infrastructure being used. For VPC, the term `zone` refers to the zone names within an MZR, such as `us-south-1`. For Classic infrastructure, the term `zone` refers to a Classic data center, such as `dal10`. {: tip} ### Classic regions with multiple data centers {: #zones-mz} If you create a classic cluster with multiple data centers, the replicas of the highly available Kubernetes master are automatically spread across the data centers. You have the option to spread your worker nodes across classic zones (data centers) to protect your apps from a zone failure. To determine whether a classic region has multiple data centers from the CLI, your can run `ibmcloud oc locations` and look for the value in the `Multizone Metro` column. {: shortdesc} ![Red Hat OpenShift on IBM Cloud Classic regions](images/locations-classic-multi.svg){: caption="Red Hat OpenShift on IBM Cloud locations" caption-side="bottom"} This image is an artistic representation and does not reflect actual political or geographic boundaries. {: note} | Geography | Country | Metro | Region | Zones | | --- | --- | --- | --- | --- | | Asia Pacific | Australia | Sydney | au-syd | syd01, syd04, syd05 | | Asia Pacific | Japan | Osaka | jp-osa | osa21, osa22, osa23 | | Asia Pacific | Japan | Tokyo | jp-tok | tok02, tok04, tok05 | | Europe | Germany | Frankfurt | de-fra | fra02, fra04, fra05 | | Europe | United Kingdom | London | uk-lon | lon02, lon04, lon05, lon06 | | North America | United States | Dallas | us-dal | dal10, dal12, dal13 | | North America | United States | Washington DC | us-wdc | wdc04, wdc06, wdc07 | {: caption="Available multizone regions for classic clusters in Red Hat OpenShift on IBM Cloud." caption-side="bottom"} {: #classic-multizone-locations-table} ### Classic regions with one data center {: #zones-sz} If you create a classic cluster in a region with only one data center, the highly available master includes three replicas on separate hosts, but is not spread across classic zones. {: shortdesc} Classic regions with one data center are managed from the regional endpoint located in the nearest region that supports classic data centers, such as `mon01` to `us-east` or `sao01` to `us-south`. ![Red Hat OpenShift on IBM Cloud Classic regions](images/locations-classic-single.svg){: caption="Red Hat OpenShift on IBM Cloud locations" caption-side="bottom"} This image is an artistic representation and does not reflect actual political or geographic boundaries. {: note} | Geography | Country | Metro | Region | Zone | Managed from region | | --- | --- | --- | --- | --- | --- | | Asia Pacific | India | Chennai | in-che | che01 | AP North (`ap-north`, `jp-tok`) | | Asia Pacific | Singapore | Singapore | sng-mtr | sng01 | AP North (`ap-north`, `jp-tok`) | | Europe | France | Paris | fr-par | par01 | EU Central (`eu-central`, `eu-de`) | | Europe | Netherlands | Amsterdam | nl-ams | ams03 | EU Central (`eu-central`, `eu-de`) | | North America | Canada | Montreal | ca-mon | mon01 | US East (`us-east`) | | North America | Canada | Toronto | ca-tor | tor01 | US East (`us-east`) | | North America | United States | San Jose | us-sjc | sjc03, sjc04 | US South (`us-south`) | | South America | Brazil | Sao Paulo | br-sao | sao01 | US South (`us-south`) | {: caption="Available single zone data centers for classic clusters in Red Hat OpenShift on IBM Cloud." caption-side="bottom"} {: #classic-single-zone-locations-table} ## Satellite regions {: #sat-regions-openshift} To see a list of the supported `Managed from` regions for Satellite clusters, [Supported Satellite locations](https://cloud.ibm.com/docs/satellite?topic=satellite-sat-regions&format=markdown). ## Where are the resources? {: #regions_resources} Where your resources are stored in the cluster depends on the availability of the cluster A cluster might be available in a single zone or multiple zones (multizone). ### Resources in single zone clusters {: #regions_single_zone} Your cluster's resources remain in the data center in which the cluster is deployed, but management operations might be routed through a regional endpoint. {: shortdesc} Your cluster's resources, including the master and worker nodes, are in the same zone that you deployed the cluster to. When you initiate local container orchestration actions, such as `oc` commands, the information is exchanged between your master and worker nodes within the same zone. If you set up other cluster resources, such as storage, networking, compute, or apps running in pods, the resources and their data remain in the data center that you deployed your cluster to. When you initiate cluster management actions, such as running **`ibmcloud oc`** commands, basic information about the cluster such as name, ID, user, the command is routed through a regional endpoint and the global endpoint. ### Resources in multizone clusters {: #regions_multizone} In multizone clusters, the cluster's resources are spread across multiple locations (zones for VPC and data centers for Classic) for higher availability. {: shortdesc} Worker nodes are spread across multiple VPC zones or Classic data centers in the region to provide more availability for your cluster. The Kubernetes master replicas are also spread across zones or classic data centers. When you initiate local container orchestration actions, such as **`oc`** commands, the information is exchanged between your master and worker nodes through the global endpoint. Other cluster resources, such as storage, networking, compute, or apps running in pods, vary in how they deploy to the zones in your cluster. For more information, review these topics: * Setting up [file storage](https://cloud.ibm.com/docs/openshift?topic=openshift-file_storage&format=markdown#add_file) and [block storage](https://cloud.ibm.com/docs/openshift?topic=openshift-block_storage&format=markdown#add_block) in clusters, or [choosing a multizone persistent storage solution](https://cloud.ibm.com/docs/openshift?topic=openshift-storage-plan&format=markdown). * [Enabling public or private access to an app by using a network load balancer (NLB) service in a cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-loadbalancer&format=markdown#multi_zone_config). * [Managing network traffic by using Ingress](https://cloud.ibm.com/docs/containers?topic=containers-managed-ingress-about&format=markdown). * [Increasing the availability of your app](https://cloud.ibm.com/docs/openshift?topic=openshift-app&format=markdown). When you initiate cluster management actions, such as running [`ibmcloud oc` commands](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-cli&format=markdown), basic information about the cluster, such as name, ID, user, the command is routed through the global endpoint.