Merge branch 'lberner_ADO_167455_update-kubernetes' of https://github.com/louisberner/azure-docs into lou-1012

Author: dansis2022

articles/databox-online/azure-stack-edge-gpu-2309-release-notes.md

@@ -7,7 +7,7 @@ author: alkohli
 ms.service: databox
 ms.subservice: edge
 ms.topic: article
-ms.date: 10/02/2023
+ms.date: 10/09/2023
 ms.author: alkohli
 ---
 
@@ -23,7 +23,8 @@ This article applies to the **Azure Stack Edge 2309** release, which maps to sof
 
 > [!Warning] 
 > In this release, you must update the packet core version to AP5GC 2308 before you update to Azure Stack Edge 2309. For detailed steps, see [Azure Private 5G Core 2308 release notes](../private-5g-core/azure-private-5g-core-release-notes-2308.md).
-> If you update to Azure Stack Edge 2309 before updating to Packet Core 2308.0.1, you will experience a total system outage. In this case, you must delete and re-create the Azure Kubernetes service cluster on your Azure Stack Edge device. 
+> If you update to Azure Stack Edge 2309 before updating to Packet Core 2308.0.1, you will experience a total system outage. In this case, you must delete and re-create the Azure Kubernetes service cluster on your Azure Stack Edge device.
+> Each time you change the Kubernetes workload profile, you are prompted for the Kubernetes update. Go ahead and apply the update.
 
 ## Supported update paths
 

articles/databox-online/azure-stack-edge-gpu-install-update.md

@@ -7,7 +7,7 @@ author: alkohli
 ms.service: databox
 ms.subservice: edge
 ms.topic: how-to
-ms.date: 10/02/2023
+ms.date: 10/05/2023
 ms.author: alkohli
 ---
 # Update your Azure Stack Edge Pro GPU 
@@ -78,6 +78,8 @@ In Azure portal, the process will require two clicks, the first update gets your
 
 From the local UI, you will have to run each update separately: update the device version to 2303, update Kubernetes version to 2210, update Kubernetes version to 2303, and then the third update gets both the device version and Kubernetes version to 2309.
 
+Each time you change the Kubernetes profile, you are prompted for the Kubernetes update. Go ahead and apply the update.
+
 ### Updates for a single-node vs two-node
 
 The procedure to update an Azure Stack Edge is the same whether it is a single-node device or a two-node cluster. This applies both to the Azure portal or the local UI procedure. 

articles/databox-online/azure-stack-edge-reset-reactivate-device.md

@@ -7,7 +7,7 @@ author: v-dalc
 ms.service: databox
 ms.subservice: edge
 ms.topic: how-to
-ms.date: 04/27/2023
+ms.date: 10/09/2023
 ms.author: alkohli
 ---
 
@@ -31,7 +31,12 @@ To wipe the data off the data disks of your device, you need to reset your devic
 Before you reset, create a copy of the local data on the device if needed. You can copy the data from the device to an Azure Storage container.
 
 >[!IMPORTANT]
-> Resetting your device will erase all local data and workloads from your device, and that can't be reversed. Reset your device only if you want to start afresh with the device.
+> - Resetting your device will erase all local data and workloads from your device, and that can't be reversed. Reset your device only if you want to start afresh with the device.
+> - If running AP5GC/SAP Kubernetes workload profiles and you updated your Azure Stack Edge to 2309, and reset your Azure Stack Edge device, you see the following behavior: 
+> -- In the local web UI, if you go to Software updates page, you see that the Kubernetes version is unavailable.
+> -- In Azure portal, you are prompted to apply a Kubernetes update.
+> Go ahead and apply the Kubernetes update.
+> -- After device reset, you must select a Kubernetes workload profile again. Otherwise, the default "Other workloads" profile will be applied. For more information, see [Configure compute IPs](azure-stack-edge-gpu-deploy-configure-network-compute-web-proxy.md?pivots=two-node#configure-compute-ips-1).  
 
 You can reset your device in the local web UI or in PowerShell. For PowerShell instructions, see [Reset your device](./azure-stack-edge-connect-powershell-interface.md#reset-your-device).