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/load-balancer-migration-guidelines.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,7 +34,7 @@ In this case, there are two options to create a cluster
34
34
35
35
**Approach 1:** Create the cluster with a new subnet
36
36
37
-
1. Choose the outbound connectivity for your cluster Follow this doc[Use Source Network Address Translation (SNAT) for outbound connections](/azure/load-balancer/load-balancer-outbound-connections), and choose one method to provide outbound connectivity for the new cluster. The most recommended way is to attach a NAT gateway and a Network Security Group (NSG) to the subnet.
37
+
1. Choose the outbound connectivity for your cluster, and follow this document[Use Source Network Address Translation (SNAT) for outbound connections](/azure/load-balancer/load-balancer-outbound-connections), and choose one method to provide outbound connectivity for the new cluster. The most recommended way is to attach a NAT gateway and a Network Security Group (NSG) to the subnet.
38
38
39
39
1. (Optional) Create a new NAT gateway and a new network security group (NSG).
40
40
@@ -43,7 +43,7 @@ In this case, there are two options to create a cluster
43
43
>
44
44
> Follow the docs [Quickstart: Create a NAT gateway - Azure portal](/azure/nat-gateway/quickstart-create-nat-gateway-portal), and [Create, change, or delete an Azure network security group](/azure/virtual-network/manage-network-security-group?tabs=network-security-group-portal#create-a-network-security-group) to create a new NAT gateway and a new network security group.
45
45
>
46
-
> You can refer to the doc[Control network traffic in Azure HDInsight](./control-network-traffic.md#hdinsight-with-network-security-groups) to set up correct NSG rules.
46
+
> You can refer to this document[Control network traffic in Azure HDInsight](./control-network-traffic.md#hdinsight-with-network-security-groups) to set up correct NSG rules.
47
47
48
48
1. Create a new subnet and associate the subnet with the NAT gateway and network security group.
49
49
@@ -66,9 +66,9 @@ To upgrade your existing custom virtual network to integrate Azure standard load
66
66
67
67
> [!NOTE]
68
68
> You could associate an existing NAT gateway and NSG or the newly created ones.
69
-
> Follow the docs[Quickstart: Create a NAT gateway - Azure portal](/azure/nat-gateway/quickstart-create-nat-gateway-portal), and [Create, change, or delete an Azure network security group](/azure/virtual-network/manage-network-security-group?tabs=network-security-group-portal#create-a-network-security-group) to create a new NAT gateway and a new network security group.
69
+
> Follow this doccument[Quickstart: Create a NAT gateway - Azure portal](/azure/nat-gateway/quickstart-create-nat-gateway-portal), and [Create, change, or delete an Azure network security group](/azure/virtual-network/manage-network-security-group?tabs=network-security-group-portal#create-a-network-security-group) to create a new NAT gateway and a new network security group.
70
70
>
71
-
> You can refer to the doc[Control network traffic in Azure HDInsight](./control-network-traffic.md#hdinsight-with-network-security-groups) to set up correct NSG rules.
71
+
> You can refer to this document[Control network traffic in Azure HDInsight](./control-network-traffic.md#hdinsight-with-network-security-groups) to set up correct NSG rules.
72
72
73
73
1. Associate the NAT gateway with your subnet along with a network security group.
74
74
@@ -84,7 +84,7 @@ To upgrade your existing custom virtual network to integrate Azure standard load
84
84
85
85
### Scenario 2: The existing subnet has HDInsight clusters with basic load balancers.
86
86
87
-
**Approach 1:** The most recommended way is to associate a NAT gateway to the subnet along with Network security group.
87
+
**Approach 1:** The most recommended way is to associate a NAT gateway to the subnet along with network security group.
88
88
89
89
According to [Azure NAT Gateway frequently asked questions](/azure/nat-gateway/faq#are-basic-sku-resources--basic-load-balancer-and-basic-public-ip-addresses--compatible-with-a-nat-gateway), the subnet with NAT gateway and Azure standard load balancer isn't compatible.
90
90
@@ -96,9 +96,9 @@ To associate with a NAT Gateway, perform the following steps.
96
96
97
97
> [!NOTE]
98
98
> You could associate an existing NAT gateway and NSG or the newly created ones.
99
-
> Follow the docs[Quickstart: Create a NAT gateway - Azure portal](/azure/nat-gateway/quickstart-create-nat-gateway-portal), and [Create, change, or delete an Azure network security group](/azure/virtual-network/manage-network-security-group?tabs=network-security-group-portal#create-a-network-security-group) to create a new NAT gateway and a new network security group.
99
+
> Follow thi document[Quickstart: Create a NAT gateway - Azure portal](/azure/nat-gateway/quickstart-create-nat-gateway-portal), and [Create, change, or delete an Azure network security group](/azure/virtual-network/manage-network-security-group?tabs=network-security-group-portal#create-a-network-security-group) to create a new NAT gateway and a new network security group.
100
100
>
101
-
> You can refer to the doc[Control network traffic in Azure HDInsight](./control-network-traffic.md#hdinsight-with-network-security-groups) to set up correct NSG rules.
101
+
> You can refer to this document[Control network traffic in Azure HDInsight](./control-network-traffic.md#hdinsight-with-network-security-groups) to set up correct NSG rules.
102
102
103
103
1. Associate the subnet with the NAT gateway and network security group.
0 commit comments