Non-RHCOS enabled locations in London

The following network requirements are for outbound connectivity for Red Hat Enterprise Linux (RHEL) hosts for use with non Red Hat CoreOS enabled locations in the London (eu-gb) region.

The type of location that you create dictates the type of operating systems that can run on your hosts. If your location is RHCOS enabled, then you can attach hosts that are running either RHEL and RHCOS. If your location isn't RHCOS enabled, then you can attach only hosts that are running RHEL. You can check whether your location is RHCOS enabled. For more information about operating system support, see Planning your operating system.

You can verify your host setup with the satellite-host-check script. For more information, see Checking your host setup.

You can download a copy of these requirements.

Review the following outbound network requirements for RHEL hosts for use with non-RHCOS enabled locations in the London (eu-gb) region.

Allow hosts to connect to IBM.

Destination hostnames: cloud.ibm.com, containers.cloud.ibm.com, api.link.satellite.cloud.ibm.com
Protocol and ports: HTTPS Port 443

Allow access to Red Hat network time protocol (NTP) servers.

Destination hostnames: 0.rhel.pool.ntp.org, 1.rhel.pool.ntp.org, 2.rhel.pool.ntp.org, 3.rhel.pool.ntp.org
Protocol and ports: Allow NTP protocol and provide UDP on port 123.

Allow hosts to communicate with Cloud Identity and Access Management.

Destination hostnames: https://iam.bluemix.net, https://iam.cloud.ibm.com
Protocol and ports: TCP 443

Your firewall must be Layer 7 to allow the IAM domain name. IAM does not have specific IP addresses that you can allow. If your firewall does not support Layer 7, you can allow all HTTPS network traffic on port 443.

Allow hosts to connect to the LaunchDarkly service.

Destination hostnames: app.launchdarkly.com,clientstream.launchdarkly.com
Protocol and ports: HTTPS 443

Allow hosts to communicate with Red Hat Container Registry.

Allow your host machines to access the required sites for OpenShift Container Platform. For more information, see Configuring your firewall.

Allow control plane nodes to communicate with the management plane.

Destination IP addresses: 158.175.120.210, 141.125.97.106, 158.176.139.66
Destination hostnames: c106.eu-gb.satellite.cloud.ibm.com, c106-1.eu-gb.satellite.cloud.ibm.com, c106-2.eu-gb.satellite.cloud.ibm.com, c106-3.eu-gb.satellite.cloud.ibm.com, c106-e.eu-gb.satellite.cloud.ibm.com
Protocol and ports: TCP 30000 - 32767 and UDP 30000 - 32767

Allow control plane nodes to back up control plane etcd data to IBM Cloud Object Storage.

Destination IP addresses: N/A
Destination hostnames: s3.eu-gb.cloud-object-storage.appdomain.cloud and *.s3.eu-gb.cloud-object-storage.appdomain.cloud
Protocol and ports: HTTPS 443

Allow continuous delivery of updates to platform components.

Destination IP addresses: N/A
Destination hostnames: s3.us.cloud-object-storage.appdomain.cloud and *.s3.us.cloud-object-storage.appdomain.cloud
Protocol and ports: HTTPS 443

Allow Link tunnel clients to connect to the Link tunnel server endpoint.

Destination IP addresses: 158.175.130.138, 141.125.87.226, 158.176.74.242
Destination hostnames: c-01-ws.eu-gb.link.satellite.cloud.ibm.com, api.link.satellite.cloud.ibm.com
Protocol and ports: HTTPS 443

You can find the hostnames or IP addresses by running the dig c-<XX>-ws.eu-gb.link.satellite.cloud.ibm.com +short command. Replace <XX> with 01, 02, and so on, until no DNS results are returned.

Allow hosts to be attached to a location and assigned to services in the location.

Destination IP addresses: 159.122.224.242, 158.175.65.170, 158.176.95.146, 104.94.220.126, 104.94.221.126, 104.94.222.134, 104.94.223.134, 104.96.176.126, 104.96.177.126, 104.96.178.128, 104.96.179.128, 104.96.180.125, 104.96.181.125
Destination hostnames: origin.eu-gb.containers.cloud.ibm.com and bootstrap.eu-gb.containers.cloud.ibm.com
Protocol and ports: HTTPS 443

Allow Akamai proxied load balancers for Satellite Config and Link API.

Akamai's source IP addresses
Destination hostnames: api.eu-gb.link.satellite.cloud.ibm.com, config.eu-gb.satellite.cloud.ibm.com, eu-gb.containers.cloud.ibm.com, config.satellite.cloud.ibm.com
Protocol and ports: HTTPS 443

Allow hosts to communicate with IBM Cloud Container Registry.

Destination IP addresses: N/A
Destination hostnames: icr.io, registry.bluemix.net, uk.icr.io, registry.eu-gb.bluemix.net
Protocol and ports: HTTPS 443

Optional: Allow hosts to communicate with IBM Cloud Log Analysis.

Destination IP addresses and hostnames: IBM Cloud Log Analysis endpoints
Protocol and ports: HTTPS 443

If you plan to use IBM Cloud Log Analysis in your Red Hat OpenShift on IBM Cloud Satellite clusters, then include these network options.

Optional: Allow hosts to communicate with IBM Cloud Monitoring.

Destination IP addresses and hostnames: Monitoring endpoints
Protocol and ports: HTTPS 443 and 6443

If you plan to use Monitoring in your Red Hat OpenShift on IBM Cloud Satellite clusters, then include these network options.