Skip to content

Commit 7d1bbbc

Browse files
authored
Improved Acrolinx Score
Improved Acrolinx Score
1 parent d46df89 commit 7d1bbbc

File tree

1 file changed

+9
-9
lines changed

1 file changed

+9
-9
lines changed

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

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.date: 03/14/2024
88

99
# Control egress traffic from HDInsight on AKS Clusters
1010

11-
[!INCLUDE [feature-in-preview](../includes/feature-in-preview.md)]
11+
[!INCLUDE [feature-in-preview](includes/feature-in-preview.md)]
1212

1313
HDInsight on AKS is a managed Platform as a Service (PaaS) that runs on Azure Kubernetes Service (AKS). HDInsight on AKS allows you to deploy popular Open-Source Analytics workloads like Apache Spark™, Apache Flink®️, and Trino without the overhead of managing and monitoring containers.
1414

@@ -35,9 +35,9 @@ Some of the most common ones are:
3535

3636
1. Use Outbound cluster pool with User defined routing to control egress traffic at the subnet level.
3737

38-
1. Use private AKS feature, the AKS control plane or API server has internal IP addresses You can ensure network traffic between AKS Control plane / API server and HDInsight on AKS node pools remains on the private network only.
38+
1. The AKS control plane, or API server has internal IP addresses. You can ensure network traffic between AKS Control plane / API server and HDInsight on AKS node pools remains on the private network only.
3939

40-
1. To avoid creating public IPs for the cluster, use private ingress feature on your clusters.
40+
1. Avoid creating public IPs for the cluster, use private ingress feature on your clusters.
4141

4242
In the following sections, we describe each method and tool in more detail.
4343

@@ -55,7 +55,7 @@ A public IP created by HDInsight on AKS, and it's an AKS-managed resource, which
5555

5656
When clusters are created, then certain ingress public IPs also get created.
5757

58-
To allow requests to be sent to the cluster, you need to [allowlist the traffic](./secure-traffic-by-nsg#inbound-security-rules-ingress-traffic.md). You can also configure certain [rules in the NSG ](./secure-traffic-by-nsg#inbound-security-rules-ingress-traffic) to do a coarse-grained control.
58+
To allow requests to be sent to the cluster, you need to [allowlist the traffic](./secure-traffic-by-nsg#inbound-security-rules-ingress-traffic). You can also configure certain [rules in the NSG ](./secure-traffic-by-nsg#inbound-security-rules-ingress-traffic) to do a coarse-grained control.
5959

6060
### Outbound with user defined routing
6161

@@ -90,7 +90,7 @@ Azure Firewall lets you control outbound traffic at a much more granular level a
9090

9191
Following is an example of setting up firewall rules, and testing your outbound connections.
9292

93-
1. Create the required firewall subnet
93+
1. Create the required firewall subnet:
9494

9595
To deploy a firewall into the integrated virtual network, you need a subnet called AzureFirewallSubnet or Name of your choice.
9696

@@ -139,7 +139,7 @@ Following is an example of setting up firewall rules, and testing your outbound
139139

140140
1. Route all traffic to the firewall
141141

142-
When you create a virtual network, Azure automatically creates a default route table for each of its subnets and adds system [default routes to the table](azure/virtual-network/virtual-networks-udr-overview#default). In this step, you create a user-defined route table that routes all traffic to the firewall, and then associate it with the App Service subnet in the integrated virtual network.
142+
When you create a virtual network, Azure automatically creates a default route table for each of its subnets and adds system [default routes to the table](/azure/virtual-network/virtual-networks-udr-overview#default). In this step, you create a user-defined route table that routes all traffic to the firewall, and then associate it with the App Service subnet in the integrated virtual network.
143143

144144
1. On the [Azure portal](https://portal.azure.com/) menu, select All services or search for and select All services from any page.
145145

@@ -248,12 +248,12 @@ The private FQDN is only for private cluster, recorded as A-RECORD in private DN
248248

249249
### Reference
250250

251-
- [Azure virtual network traffic routing | Microsoft Learn](https://learn.microsoft.com/en-us/azure/virtual-network/virtual-networks-udr-overview).
251+
- [Azure virtual network traffic routing | Microsoft Learn](https://learn.microsoft.com/azure/virtual-network/virtual-networks-udr-overview).
252252

253-
- [Azure Virtual Network peering | Microsoft Learn](https://learn.microsoft.com/en-us/azure/virtual-network/virtual-network-peering-overview).
253+
- [Azure Virtual Network peering | Microsoft Learn](https://learn.microsoft.com/azure/virtual-network/virtual-network-peering-overview).
254254

255255
- [Outbound traffic on HDInsight on AKS - Azure HDInsight on AKS | Microsoft Learn.](./required-outbound-traffic)
256256

257-
- [Outbound network and FQDN rules for Azure Kubernetes Service (AKS) clusters - Azure Kubernetes Service | Microsoft Learn](https://learn.microsoft.com/en-us/azure/aks/outbound-rules-control-egress#azure-global-required-network-rules).
257+
- [Outbound network and FQDN rules for Azure Kubernetes Service (AKS) clusters - Azure Kubernetes Service | Microsoft Learn](https://learn.microsoft.com/azure/aks/outbound-rules-control-egress#azure-global-required-network-rules).
258258

259259

0 commit comments

Comments
 (0)