From 3aee8893b80a8a9bca35855592f3f38a0c3e90a0 Mon Sep 17 00:00:00 2001 From: AedinC Date: Thu, 11 Dec 2025 10:30:29 +0000 Subject: [PATCH] OSDOCS-17623:Update Google Cloud firewall prereqs. --- .../cloud-experts-osd-create-new-limit-egress.adoc | 5 ----- modules/osd-gcp-psc-firewall-prerequisites.adoc | 9 --------- 2 files changed, 14 deletions(-) diff --git a/cloud_experts_osd_tutorials/cloud-experts-osd-create-new-limit-egress.adoc b/cloud_experts_osd_tutorials/cloud-experts-osd-create-new-limit-egress.adoc index a41d681c6dd6..6da389a5e936 100644 --- a/cloud_experts_osd_tutorials/cloud-experts-osd-create-new-limit-egress.adoc +++ b/cloud_experts_osd_tutorials/cloud-experts-osd-create-new-limit-egress.adoc @@ -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] diff --git a/modules/osd-gcp-psc-firewall-prerequisites.adoc b/modules/osd-gcp-psc-firewall-prerequisites.adoc index 5f91d9b50121..0835e7253619 100644 --- a/modules/osd-gcp-psc-firewall-prerequisites.adoc +++ b/modules/osd-gcp-psc-firewall-prerequisites.adoc @@ -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`.