Skip to content

Commit 49b7b21

Browse files
committed
Removed reference for two-node configuration from Pro-R article.
1 parent 2136405 commit 49b7b21

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/databox-online/azure-stack-edge-pro-r-deploy-configure-network-compute-web-proxy.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -157,7 +157,7 @@ After the virtual switches are created, you can enable the switches for Kubernet
157157
1. From the dropdown list, select the virtual switch you want to enable for Kubernetes compute traffic.
158158
1. Assign **Kubernetes node IPs**. These static IP addresses are for the Kubernetes VMs.
159159

160-
If you select the **Azure Private MEC solution** or **SAP Digital Manufacturing for Edge Computing or another Microsoft partner** workload option for your environment, you must provide a contiguous range of a minimum of 6 IPv4 addresses (or more) for a 1-node configuration, and 7 IPv4 addresses (or more) for a two-node configuration.
160+
If you select the **Azure Private MEC solution** or **SAP Digital Manufacturing for Edge Computing or another Microsoft partner** workload option for your environment, you must provide a contiguous range of a minimum of 6 IPv4 addresses (or more) for a 1-node configuration.
161161

162162
If you select the **other workloads** option for an *n*-node device, a contiguous range of a minimum of *n+1* IPv4 addresses (or more) are provided for the compute VM using the start and end IP addresses. For a 1-node device, provide a minimum of 2 free, contiguous IPv4 addresses.
163163

0 commit comments

Comments
 (0)