openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Code Issues Releases Activity

OSDOCS-17623:Update Google Cloud firewall prereqs.

Browse Source
This commit is contained in:
AedinC
2025-12-11 10:30:29 +00:00
committed by openshift-cherrypick-robot
parent 9b66af8e0a
commit 040c5e0f13
2 changed files with 0 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
cloud_experts_osd_tutorials/cloud-experts-osd-create-new-limit-egress.adoc
View File

@@ -10,11 +10,6 @@ toc::[]
[role="_abstract"]
Use this guide to implement egress restrictions for {product-title} on {GCP} by using {GCP}'s Next Generation Firewall (NGFW). NGFW is a fully distributed firewall service that allows fully qualified domain name (FQDN) objects in firewall policy rules. This is necessary for many of the external endpoints that {product-title} relies on.
[IMPORTANT]
====
The ability to restrict egress traffic using a firewall or other network device is only supported with {product-title} clusters deployed using Private Service Connect (PSC). Clusters that do not use PSC require a support exception to use this functionality. For additional assistance, please open a link:https://access.redhat.com/support/cases/?extIdCarryOver=true&sc_cid=701f2000001Css5AAC#/case/new/get-support?caseCreate=true[support case].
====
include::modules/cloud-experts-osd-limit-egress-ngfw-prereqs.adoc[leveloffset=+1]
include::modules/cloud-experts-osd-limit-egress-ngfw-setup-environ.adoc[leveloffset=+1]

9
modules/osd-gcp-psc-firewall-prerequisites.adoc
View File

@@ -8,11 +8,6 @@
If you are using a firewall to control egress traffic from {product-title} on {GCP}, you must configure your firewall to grant access to certain domains and port combinations listed in the tables below. {product-title} requires this access to provide a fully managed OpenShift service.
[IMPORTANT]
====
Only {product-title} on {GCP} clusters deployed with Private Service Connect can use a firewall to control egress traffic.
====
// .Prerequisites
// Per SMEs, no prereqs. Will confirm with QE when ticket is reviewed.
@@ -70,10 +65,6 @@ Only {product-title} on {GCP} clusters deployed with Private Service Connect can
|443
|Required. Allows interactions between the cluster and {cluster-manager-first} to enable functionality, such as scheduling upgrades.
|`sso.redhat.com`
|443
|The `https://console.redhat.com/openshift` site uses authentication from `sso.redhat.com`.
|`catalog.redhat.com`
|443
|The `registry.access.redhat.com` and `https://registry.redhat.io` sites redirect through `catalog.redhat.com`.