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/hdinsight-aks/control-egress-traffic-from-hdinsight-on-aks-clusters.md
+5-6Lines changed: 5 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Control network traffic from HDInsight on AKS Clusters
3
3
description: A guide to configure and manage inbound and outbound network connections from HDInsight on AKS.
4
4
ms.service: hdinsight-aks
5
5
ms.topic: how-to
6
-
ms.date: 03/19/2024
6
+
ms.date: 03/21/2024
7
7
---
8
8
9
9
# Control network traffic from HDInsight on AKS Clusters
@@ -30,14 +30,13 @@ For example, you may want to:
30
30
There are several methods and tools for controlling egress traffic from HDInsight on AKS clusters, by configuring the settings at cluster pool and cluster levels.
31
31
32
32
Some of the most common ones are:
33
+
* Use Azure Firewall or Network Security Groups (NSGs) to control egress traffic, when you opt to use outbound cluster pool with load balancer
33
34
34
-
1. Use Azure Firewall or Network Security Groups (NSGs) to control egress traffic, when you opt to use outbound cluster pool with load balancer
35
+
* Use Outbound cluster pool with User defined routing to control egress traffic at the subnet level.
35
36
36
-
1. Use Outbound cluster pool with User defined routing to control egress traffic at the subnet level.
37
+
* Use Private AKS cluster feature - To ensure AKS control plane, or API server has internal IP addresses. The network traffic between AKS Control plane / API server and HDInsight on AKS node pools (clusters) remains on the private network only.
37
38
38
-
1. Use Private AKS cluster feature - To ensure AKS control plane, or API server has internal IP addresses. The network traffic between AKS Control plane / API server and HDInsight on AKS node pools (clusters) remains on the private network only.
39
-
40
-
1. Avoid creating public IPs for the cluster, use private ingress feature on your clusters.
39
+
* Avoid creating public IPs for the cluster, use private ingress feature on your clusters.
41
40
42
41
In the following sections, we describe each method in detail.
0 commit comments