Skip to content

Commit b03eeed

Browse files
authored
Resolved review Comments
Resolved review Comments
1 parent da65444 commit b03eeed

File tree

1 file changed

+5
-6
lines changed

1 file changed

+5
-6
lines changed

articles/hdinsight-aks/control-egress-traffic-from-hdinsight-on-aks-clusters.md

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Control network traffic from HDInsight on AKS Clusters
33
description: A guide to configure and manage inbound and outbound network connections from HDInsight on AKS.
44
ms.service: hdinsight-aks
55
ms.topic: how-to
6-
ms.date: 03/19/2024
6+
ms.date: 03/21/2024
77
---
88

99
# Control network traffic from HDInsight on AKS Clusters
@@ -30,14 +30,13 @@ For example, you may want to:
3030
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.
3131

3232
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
3334

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.
3536

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.
3738

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.
4140

4241
In the following sections, we describe each method in detail.
4342

0 commit comments

Comments
 (0)