Skip to content

Commit b53af2c

Browse files
authored
Merge pull request #72991 from EricPonvelle/OSDOCS-9949_Remove-Egress-Section
OSDOCS-9949: Removed an egress section from the ROSA docs
2 parents 7951ab1 + ef71af5 commit b53af2c

File tree

1 file changed

+0
-2
lines changed

1 file changed

+0
-2
lines changed

modules/nw-egress-ips-about.adoc

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -169,7 +169,6 @@ On Azure, the following capacity limits exist for IP address assignment:
169169
- Per virtual network, the maximum number of assigned IP addresses cannot exceed 65,536.
170170

171171
For more information, see link:https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/azure-subscription-service-limits?toc=/azure/virtual-network/toc.json#networking-limits[Networking limits].
172-
endif::openshift-rosa[]
173172

174173
[id="nw-egress-ips-multi-nic-considerations_{context}"]
175174
== Considerations for using an egress IP on additional network interfaces
@@ -196,7 +195,6 @@ You can determine which other network interfaces might support egress IPs by ins
196195
OVN-Kubernetes provides a mechanism to control and direct outbound network traffic from specific namespaces and pods. This ensures that it exits the cluster through a particular network interface and with a specific egress IP address.
197196
====
198197

199-
ifndef::openshift-rosa[]
200198
[discrete]
201199
[id="nw-egress-ips-multi-nic-requirements_{context}"]
202200
=== Requirements for assigning an egress IP to a network interface that is not the primary network interface

0 commit comments

Comments
 (0)