Merge branch 'lberner-ADO-iot-edge-managed-not-supported' of https://github.com/LouisBerner/azure-docs into v-loberner-ADO-convert-iot-edge-update

Author: LouisBerner

articles/databox-online/TOC.yml

@@ -406,22 +406,6 @@
             href: azure-stack-edge-gpu-deploy-iot-edge-linux-vm.md
           - name: Nvidia DeepStream module
             href: azure-stack-edge-deploy-nvidia-deepstream-module.md
-      - name: Deploy IoT Edge samples (Managed)
-        items:
-          - name: Module from Nvidia gallery
-            href: azure-stack-edge-gpu-configure-gpu-modules.md 
-          - name: GPU module from Git repo
-            href: azure-stack-edge-gpu-deploy-sample-module.md 
-          - name: GPU module via Marketplace
-            href: azure-stack-edge-gpu-deploy-sample-module-marketplace.md 
-          - name: Modules from FPGA devices
-            href: azure-stack-edge-gpu-modify-fpga-modules-gpu.md
-          - name: Module via Azure portal 
-            href: azure-stack-edge-gpu-deploy-compute-module-simple.md
-          - name: Sync data from local share
-            href: https://github.com/Azure-Samples/azure-stack-edge-deploy-vms/blob/master/Scripts/IotEdgeScript/README.md
-          - name: Move to Linux VMs
-            href: azure-stack-edge-move-to-self-service-iot-edge.md
       - name: Troubleshoot IoT Edge issues
         href: azure-stack-edge-gpu-troubleshoot-iot-edge.md
 

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

@@ -7,7 +7,7 @@ author: alkohli
 ms.service: databox
 ms.subservice: edge
 ms.topic: tutorial
-ms.date: 10/14/2022
+ms.date: 03/25/2024
 ms.author: alkohli
 # Customer intent: As an IT admin, I need to understand how to connect and activate Azure Stack Edge Pro R so I can use it to transfer data to Azure. 
 ---
@@ -140,31 +140,41 @@ You can add or delete virtual networks associated with your virtual switches. To
 
 ## Configure compute IPs
 
-Follow these steps to configure compute IPs for your Kubernetes workloads.
+After the virtual switches are created, you can enable the switches for Kubernetes compute traffic.
 
 1. In the local UI, go to the **Kubernetes** page.
-1. From the dropdown select a virtual switch that you will use for Kubernetes compute traffic. <!--By default, all switches are configured for management. You can't configure storage intent as storage traffic was already configured based on the network topology that you selected earlier.-->
+1. Specify a workload from the options provided.
+   - If you're working with an Azure Private MEC solution, select the option for **an Azure Private MEC solution in your environment**.
+   - If you're working with an SAP Digital Manufacturing solution or another Microsoft partner solution, select the option for **a SAP Digital Manufacturing for Edge Computing or another Microsoft partner solution in your environment**.
+   - For other workloads, select the option for **other workloads in your environment**.
 
-1. Assign **Kubernetes node IPs**. These static IP addresses are for the Kubernetes VMs.
+    If prompted, confirm the option you specified and then select **Apply**.
 
-   - 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 two, free, contiguous IPv4 addresses.
+    To use PowerShell to specify the workload, see detailed steps in [Change Kubernetes workload profiles](azure-stack-edge-gpu-connect-powershell-interface.md#change-kubernetes-workload-profiles).
 
+   ![Screenshot of the Workload selection options on the Kubernetes page of the local UI for two node.](./media/azure-stack-edge-pro-r-deploy-configure-network-compute-web-proxy/azure-stack-edge-kubernetes-workload-selection.png)
 
-   > [!IMPORTANT]
-   > - Kubernetes on Azure Stack Edge uses 172.27.0.0/16 subnet for pod and 172.28.0.0/16 subnet for service. Make sure that these are not in use in your network. If these subnets are already in use in your network, you can change these subnets by running the ```Set-HcsKubeClusterNetworkInfo``` cmdlet from the PowerShell interface of the device. For more information, see Change Kubernetes pod and service subnets. <!--Target URL not available.-->
-   > - DHCP mode is not supported for Kubernetes node IPs. If you plan to deploy IoT Edge/Kubernetes, you must assign static Kubernetes IPs and then enable IoT role. This will ensure that static IPs are assigned to Kubernetes node VMs.
-   > - If your datacenter firewall is restricting or filtering traffic based on source IPs or MAC addresses, make sure that the compute IPs (Kubernetes node IPs) and MAC addresses are on the allowed list. The MAC addresses can be specified by running the ```Set-HcsMacAddressPool``` cmdlet on the PowerShell interface of the device.
+1. From the dropdown list, select the virtual switch you want to enable for Kubernetes compute traffic.
+1. Assign **Kubernetes node IPs**. These static IP addresses are for the Kubernetes VMs.  
 
-1. Assign **Kubernetes external service IPs**. These are also the load-balancing IP addresses. These contiguous IP addresses are for services that you want to expose outside of the Kubernetes cluster and you specify the static IP range depending on the number of services exposed.
+    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.
 
-   > [!IMPORTANT]
-   > We strongly recommend that you specify a minimum of one IP address for Azure Stack Edge Hub service to access compute modules. You can then optionally specify additional IP addresses for other services/IoT Edge modules (1 per service/module) that need to be accessed from outside the cluster. The service IP addresses can be updated later.
+    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.
 
+    > [!IMPORTANT]
+    > - If you're running **other workloads** in your environment, Kubernetes on Azure Stack Edge uses 172.27.0.0/16 subnet for pod and 172.28.0.0/16 subnet for service. Make sure that these are not in use in your network. For more information, see [Change Kubernetes pod and service subnets](azure-stack-edge-gpu-connect-powershell-interface.md#change-kubernetes-pod-and-service-subnets).
+    > - DHCP mode is not supported for Kubernetes node IPs.
+
+1. Assign **Kubernetes external service IPs**. These are also the load-balancing IP addresses. These contiguous IP addresses are for services that you want to expose outside of the Kubernetes cluster and you specify the static IP range depending on the number of services exposed. 
+    
+    > [!IMPORTANT]
+    > We strongly recommend that you specify a minimum of 1 IP address for Azure Stack Edge Hub service to access compute modules. The service IP addresses can be updated later. 
+    
 1. Select **Apply**.
 
-   ![Screenshot of "Advanced networking" page in local UI with fully configured Add virtual switch blade for one node.](./media/azure-stack-edge-pro-r-deploy-configure-network-compute-web-proxy/compute-virtual-switch-1.png) 
+    ![Screenshot of Configure compute page in Advanced networking in local UI 2.](./media/azure-stack-edge-pro-r-deploy-configure-network-compute-web-proxy/configure-compute-network-2.png)
 
-1. The configuration takes a couple minutes to apply and you may need to refresh the browser.
+1. The configuration takes a couple minutes to apply and you may need to refresh the browser. 
 
 1. Select **Next: Web proxy** to configure web proxy.