RHCOS enabled locations in Washington D.C.
The following network requirements are for outbound connectivity for Red Hat Enterprise Linux (RHEL) and Red Hat CoreOS (RHCOS) hosts for use with Red Hat CoreOS enabled locations in the Washington D.C. (us-east) 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 and RHCOS hosts for use with RHCOS enabled locations in the Washington D.C. (us-east) region.
- 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
- Destination hostnames:
-
If you don't want to use Red Hat network time protocol (NTP) servers, you can instead define a custom NTP server for your RHCOS hosts.
- Allow hosts to communicate with Red Hat Container Registry.
-
Allow your hosts 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: 169.55.87.98, 169.63.138.34, 169.62.47.42
- Destination hostnames:
c121.us-east.satellite.cloud.ibm.com,c121-1.us-east.satellite.cloud.ibm.com,c121-2.us-east.satellite.cloud.ibm.com,c121-3.us-east.satellite.cloud.ibm.com,c121-e.us-east.satellite.cloud.ibm.com - Protocol and ports: TCP 30000 - 32767
- Allow hosts to be attached to a location and assigned to services in the location.
-
- Destination IP addresses: 169.63.88.186, 169.60.73.142, 169.61.109.34, 104.94.220.128, 104.94.221.128, 104.94.222.136, 104.94.223.136, 104.96.176.128, 104.96.177.128, 104.96.178.130, 104.96.179.130, 104.96.180.127, 104.96.181.127
- Destination hostnames:
origin.us-east.containers.cloud.ibm.comandbootstrap.us-east.containers.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,us.icr.io,registry.bluemix.net,registry.ng.bluemix.net - Protocol and ports: HTTPS 443
- Allow Link tunnel clients to connect to the Link tunnel server endpoint.
-
- Destination IP addresses: 169.47.156.154, 169.63.148.250, 169.62.1.34
- Destination hostnames:
c-01-ws.us-east.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.us-east.link.satellite.cloud.ibm.com +shortcommand. Replace<XX>with01,02, and so on, until no DNS results are returned. - 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.