Alibaba
If you use a firewall, you must configure it so that OpenShift Container Platform can access the sites that it requires to function. You must always grant access to some sites, and you grant access to more if you use Red Hat Insights, the Telemetry service, a cloud to host your cluster, and certain build strategies.
Before you install OpenShift Container Platform, you must configure your firewall to grant access to the sites that OpenShift Container Platform requires. When using a firewall, make additional configurations to the firewall so that OpenShift Container Platform can access the sites that it requires to function.
There are no special configuration considerations for services running on only controller nodes compared to worker nodes.
If your environment has a dedicated load balancer in front of your OpenShift Container Platform cluster, review the allowlists between your firewall and load balancer to prevent unwanted network restrictions to your cluster. |
Set the following registry URLs for your firewall’s allowlist:
URL | Port | Function |
---|---|---|
|
443 |
Provides core container images |
|
443 |
Hosts a signature store that a container client requires for verifying images pulled from |
|
443 |
Hosts all the container images that are stored on the Red Hat Ecosystem Catalog, including core container images. |
|
443 |
Provides core container images |
|
443 |
Provides core container images |
|
443 |
Provides core container images |
|
443 |
Provides core container images |
|
443 |
Provides core container images |
|
443 |
Provides core container images |
|
443 |
Provides core container images |
|
443 |
Provides core container images |
|
443 |
The |
You can use the wildcards *.quay.io
and *.openshiftapps.com
instead of cdn.quay.io
and cdn0[1-6].quay.io
in your allowlist.
You can use the wildcard *.access.redhat.com
to simplify the configuration and ensure that all subdomains, including registry.access.redhat.com
, are allowed.
When you add a site, such as quay.io
, to your allowlist, do not add a wildcard entry, such as *.quay.io
, to your denylist. In most cases, image registries use a content delivery network (CDN) to serve images. If a firewall blocks access, image downloads are denied when the initial download request redirects to a hostname such as cdn01.quay.io
.
Set your firewall’s allowlist to include any site that provides resources for a language or framework that your builds require.
If you do not disable Telemetry, you must grant access to the following URLs to access Red Hat Insights:
URL | Port | Function |
---|---|---|
|
443 |
Required for Telemetry |
|
443 |
Required for Telemetry |
|
443 |
Required for Telemetry |
|
443 |
Required for Telemetry and for |
If you use Alibaba Cloud, Amazon Web Services (AWS), Microsoft Azure, or Google Cloud Platform (GCP) to host your cluster, you must grant access to the URLs that offer the cloud provider API and DNS for that cloud:
Cloud | URL | Port | Function |
---|---|---|---|
Alibaba |
|
443 |
Required to access Alibaba Cloud services and resources. Review the Alibaba endpoints_config.go file to find the exact endpoints to allow for the regions that you use. |
AWS |
|
443 |
Used to install and manage clusters in an AWS environment. |
Alternatively, if you choose to not use a wildcard for AWS APIs, you must include the following URLs in your allowlist: |
443 |
Required to access AWS services and resources. Review the AWS Service Endpoints in the AWS documentation to find the exact endpoints to allow for the regions that you use. |
|
|
443 |
Used to install and manage clusters in an AWS environment. |
|
|
443 |
Used to install and manage clusters in an AWS environment. |
|
|
443 |
Used to install and manage clusters in an AWS environment. |
|
|
443 |
Used to install and manage clusters in an AWS environment. |
|
|
443 |
Used to install and manage clusters in an AWS environment. |
|
|
443 |
Used to install and manage clusters in an AWS environment. |
|
|
443 |
Used to install and manage clusters in an AWS environment. |
|
|
443 |
Used to install and manage clusters in an AWS environment. |
|
|
443 |
Used to install and manage clusters in an AWS environment. |
|
|
443 |
Used to install and manage clusters in an AWS environment. This endpoint is always |
|
|
443 |
Used to install and manage clusters in an AWS environment. |
|
|
443 |
Used to install and manage clusters in an AWS environment. |
|
|
443 |
Required. Used to confirm quotas for deploying the service. |
|
|
443 |
Allows the assignment of metadata about AWS resources in the form of tags. |
|
|
443 |
Used to provide access to CloudFront. If you use the AWS Security Token Service (STS) and the private S3 bucket, you must provide access to CloudFront. |
|
GCP |
|
443 |
Required to access GCP services and resources. Review Cloud Endpoints in the GCP documentation to find the endpoints to allow for your APIs. |
|
443 |
Required to access your GCP account. |
|
Microsoft Azure |
|
443 |
Required to access Microsoft Azure services and resources. Review the Microsoft Azure REST API reference in the Microsoft Azure documentation to find the endpoints to allow for your APIs. |
|
443 |
Required to download Ignition files. |
|
|
443 |
Required to access Microsoft Azure services and resources. Review the Azure REST API reference in the Microsoft Azure documentation to find the endpoints to allow for your APIs. |
Allowlist the following URLs:
URL | Port | Function |
---|---|---|
|
443 |
Required to access the default cluster routes unless you set an ingress wildcard during installation. |
|
443 |
Required both for your cluster token and to check if updates are available for the cluster. |
|
443 |
Required for your cluster token. |
|
443 |
Required to access mirrored installation content and images. This site is also a source of release image signatures, although the Cluster Version Operator needs only a single functioning source. |
|
443 |
Required to access Quay image content in AWS. |
|
443 |
Required to download Red Hat Enterprise Linux CoreOS (RHCOS) images. |
|
443 |
The |
|
443 |
A source of release image signatures, although the Cluster Version Operator needs only a single functioning source. |
Operators require route access to perform health checks. Specifically, the authentication and web console Operators connect to two routes to verify that the routes work. If you are the cluster administrator and do not want to allow *.apps.<cluster_name>.<base_domain>
, then allow these routes:
oauth-openshift.apps.<cluster_name>.<base_domain>
console-openshift-console.apps.<cluster_name>.<base_domain>
, or the hostname
that is specified in the spec.route.hostname
field of the
consoles.operator/cluster
object if the field is not empty.
Allowlist the following URLs for optional third-party content:
URL | Port | Function |
---|---|---|
|
443 |
Required for all third-party images and certified operators. |
|
443 |
Provides access to container images hosted on |
|
443 |
Required for Sonatype Nexus, F5 Big IP operators. |
If you use a default Red Hat Network Time Protocol (NTP) server allow the following URLs:
1.rhel.pool.ntp.org
2.rhel.pool.ntp.org
3.rhel.pool.ntp.org
If you do not use a default Red Hat NTP server, verify the NTP server for your platform and allow it in your firewall. |