Skip to content

Commit 49ee1e4

Browse files
authored
non-sequential lists
1 parent 4ce359e commit 49ee1e4

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/hdinsight-aks/release-notes/hdinsight-aks-release-notes.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -45,10 +45,10 @@ You can refer to [What's new](../whats-new.md) page for all the details of the f
4545

4646
With private clusters, and outbound cluster settings you can now control ingress and egress traffic from HDInsight on AKS cluster pools and clusters.
4747

48-
1. Use Azure Firewall or Network Security Groups (NSGs) to control the egress traffic, when you opt to use outbound cluster pool with load balancer.
49-
1. Use Outbound cluster pool with User defined routing to control egress traffic at the subnet level.
50-
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.
51-
1. Avoid creating public IPs for the cluster. Use private ingress feature on your clusters.
48+
- Use Azure Firewall or Network Security Groups (NSGs) to control the egress traffic, when you opt to use outbound cluster pool with load balancer.
49+
- Use Outbound cluster pool with User defined routing to control egress traffic at the subnet level.
50+
- 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.
51+
- Avoid creating public IPs for the cluster. Use private ingress feature on your clusters.
5252

5353
**In place Upgrade**
5454

0 commit comments

Comments
 (0)