Locations
IBM Cloud resources are organized into a hierarchy of geographic locations. Red Hat OpenShift on IBM Cloud is available in a subset of the IBM Cloud locations, including worldwide multizone regions (MZRs) and single-campus multizone regions (SC-MZRs).
This image is an artistic representation and does not reflect actual political or geographic boundaries.
Red Hat OpenShift on IBM Cloud locations
Availability of a cluster is based on the type of cluster it is and how many replicas of the resources you have.
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
.
Classic regions with multiple data centers
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.
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 |
Classic regions with one data center
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.
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
.
The Milan (mil01
) datacenter is deprecated and closes on 31 October 2025. Migrate your Red Hat OpenShift on IBM Cloud on IBM Cloud clusters currently hosted in mil01
to another IBM Cloud datacenter by 31 October 2025.
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 | Italy | Milan | it-mil | mil01 | 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 ) |
VPC multizone regions
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.
Geography | Country | Metro | Region | Zones |
---|---|---|---|---|
Asia Pacific | Australia | Sydney | au-syd | au-syd-1, au-syd-2, au-syd-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 | † 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 |
†
These regions are available as multizone regions for clusters on VPC infrastructure only.
Satellite regions
To see a list of the supported Managed from
regions for Satellite clusters, Supported Satellite locations.
Where are the 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
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.
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
In multizone clusters, the cluster's resources are spread across multiple locations (zones for VPC and data centers for Classic) for higher availability.
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 and block storage in clusters, or choosing a multizone persistent storage solution.
- Enabling public or private access to an app by using a network load balancer (NLB) service in a cluster.
- Managing network traffic by using Ingress.
- Increasing the availability of your app.
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 the global endpoint.