You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/openshift/concepts-networking.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,7 +35,7 @@ The following list covers important networking components in an Azure Red Hat Op
35
35
* This endpoint balances internal service traffic. For this load balancer, the worker nodes are in the backend pool.
36
36
* This load balancer isn't created by default. It's created once you create a service of type LoadBalancer with the correct annotations. For example: service.beta.kubernetes.io/azure-load-balancer-internal: "true".
37
37
38
-
***aro-internal-lb**
38
+
***aro**
39
39
* This endpoint is used for any public traffic. When you create an application and a route, this endpoint is the path for ingress traffic.
40
40
* This load balancer also covers egress Internet connectivity from any pod running in the worker nodes through Azure Load Balancer outbound rules.
41
41
* Currently outbound rules aren't configurable. They allocate 1,024 TCP ports to each node.
0 commit comments