Add codespace issue

Author: PatAltimore

articles/iot-operations/troubleshoot/known-issues.md

@@ -6,7 +6,7 @@ ms.author: dobett
 ms.topic: troubleshooting-known-issue
 ms.custom:
   - ignite-2023
-ms.date: 11/07/2024
+ms.date: 12/12/2024
 ---
 
 # Known issues: Azure IoT Operations
@@ -25,6 +25,8 @@ This article lists the known issues for Azure IoT Operations.
 
 - If your deployment fails with the message `Error occurred while creating custom resources needed by system extensions`, you have encountered a known sporadic failure that will be fixed in a future release. As a work around, please delete Azure IoT Operations from your cluster using the [az iot ops delete](/cli/azure/iot/ops#az-iot-ops-delete) command and pass the `--include-deps` flag. Once Azure IoT Operations and its dependencies have been deleted from your cluster, the deployment can be retried.
 
+- If you deploy Azure IoT Operations in GitHub Codespaces, shutting down and restarting the Codespace causes a `This codespace is currently running in recovery mode due to a configuration error.` issue. Currently, there's no workaround for the issue. If you need a cluster that supports shutting down and restarting, choose one of the options in [Prepare your Azure Arc-enabled Kubernetes cluster](../deploy-iot-ops/howto-prepare-cluster.md).
+
 ## MQTT broker
 
 - MQTT broker resources created in your cluster using Kubernetes aren't visible Azure portal. This is expected because [managing Azure IoT Operations components using Kubernetes is in preview](../deploy-iot-ops/howto-manage-update-uninstall.md#preview-manage-components-using-kubernetes-deployment-manifests), and synchronizing resources from the edge to the cloud isn't currently supported.