Skip to content

Commit 9972878

Browse files
authored
Merge pull request #87234 from EricPonvelle/OSDOCS-10249_2-Egress-Lockdown-fixes
OSDOCS-10249.2: Updates to Egress lockdown
2 parents bc53a1f + d417971 commit 9972878

File tree

2 files changed

+15
-0
lines changed

2 files changed

+15
-0
lines changed

_topic_maps/_topic_map_rosa.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -263,6 +263,8 @@ Topics:
263263
File: rosa-hcp-creating-cluster-with-aws-kms-key
264264
- Name: Creating a private cluster on ROSA with HCP
265265
File: rosa-hcp-aws-private-creating-cluster
266+
- Name: Creating a ROSA with HCP cluster with egress lockdown
267+
File: rosa-hcp-egress-lockdown-install
266268
- Name: Creating ROSA with HCP clusters with external authentication
267269
File: rosa-hcp-sts-creating-a-cluster-ext-auth
268270
- Name: Creating ROSA with HCP clusters without a CNI plugin

rosa_release_notes/rosa-release-notes.adoc

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,15 @@ toc::[]
1616
[id="rosa-q1-2025_{context}"]
1717
=== Q1 2025
1818

19+
// These notes need to be duplicated until the ROSA with HCP split out is completed.
20+
ifdef::openshift-rosa[]
21+
[IMPORTANT]
22+
====
23+
Egress lockdown is a Technology Preview feature.
24+
====
25+
26+
* **Egress lockdown is now available as a Technology Preview on {product-title} clusters.** You can create a fully operational cluster that does not require a public egress by configuring a virtual private cloud (VPC) and using the `--properties zero_egress:true` flag when creating your cluster. For more information, see xref:../rosa_hcp/rosa-hcp-egress-lockdown-install.adoc#rosa-hcp-egress-lockdown-install[Creating a {product-title} cluster with egress lockdown].
27+
endif::openshift-rosa[]
1928
ifdef::openshift-rosa-hcp[]
2029
[IMPORTANT]
2130
====
@@ -190,6 +199,10 @@ endif::openshift-rosa[]
190199
[id="rosa-known-issues_{context}"]
191200
== Known issues
192201

202+
// These notes need to be duplicated until the ROSA with HCP split out is completed.
203+
ifdef::openshift-rosa[]
204+
* While egress lockdown works across all supported versions of ROSA, Red Hat suggests you upgrade your cluster or build a cluster to the latest z-stream for your {ocp}. Due to an upstream issue with the internal image registry functionality in disconnected environments, you may experience issues with various {ocp} components within your cluster until you upgrade your version of HCP to the latest z-stream. If you are using older z-stream ROSA clusters with the egress lockdown feature, you must include a public route to the internet from your cluster. See link:https://issues.redhat.com/browse/OCPBUGS-44314[OCPBUGS-44314] for further details.
205+
endif::openshift-rosa[]
193206
ifdef::openshift-rosa-hcp[]
194207
* While egress lockdown works across all supported versions of ROSA, Red Hat suggests you upgrade your cluster or build a cluster to the latest z-stream for your {ocp}. Due to an upstream issue with the internal image registry functionality in disconnected environments, you may experience issues with various {ocp} components within your cluster until you upgrade your version of HCP to the latest z-stream. If you are using older z-stream ROSA clusters with the egress lockdown feature, you must include a public route to the internet from your cluster. See link:https://issues.redhat.com/browse/OCPBUGS-44314[OCPBUGS-44314] for further details.
195208
endif::openshift-rosa-hcp[]

0 commit comments

Comments
 (0)