Merge pull request #289529 from kgremban/patch-2

Update known-issues for deployment

Author: prmerger-automator[bot]

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

@@ -17,22 +17,11 @@ This article lists the known issues for Azure IoT Operations Preview.
 
 ## Deploy and uninstall issues
 
-- If you prefer to have no updates made to your cluster without giving explicit consent, you should disable Arc updates when you enable the cluster. This is due to the fact that some system extensions are automatically updated by the Arc agent.
-
-- Using your own cert-manager issuer is only supported for cert-manager versions less than 1.13.
-
-- The Azure storage account that you use for the schema registry must have public network access enabled.
+- If you prefer to have no updates made to your cluster without giving explicit consent, you should disable Arc updates when you enable the cluster. This is due to the fact that some system extensions are automatically updated by the Arc agent. To disable updates, include the `--disable-auto-upgrade` flag as part of the `az connectedk8s connect` command.
 
 - If your deployment fails with the `"code":"LinkedAuthorizationFailed"` error, it means that you don't have **Microsoft.Authorization/roleAssignments/write** permissions on the resource group that contains your cluster.
 
-  To resolve this issue, either request the required permissions or make the following adjustments to your deployment steps:
-
-  - If deploying with an Azure Resource Manager template, set the `deployResourceSyncRules` parameter to `false`.
-  - If deploying with the Azure CLI, include the `--disable-rsync-rules` flag with the [az iot ops init](/cli/azure/iot/ops#az-iot-ops-init) command.
-
-- Directly editing **SecretProviderClass** and **SecretSync** custom resources in your Kubernetes cluster can the break secrets flow in Azure IoT Operations. For any operations related to secrets, use the operations experience UI.
-
-- By default, the `az iot ops check` command displays warning about missing dataflows until you create a dataflow.
+- Directly editing **SecretProviderClass** and **SecretSync** custom resources in your Kubernetes cluster can break the secrets flow in Azure IoT Operations. For any operations related to secrets, use the operations experience UI.
 
 ## MQTT broker