Merge pull request #290750 from kgremban/nov19-proxy

Hardware reqs; proxy-skip-range

Author: prmerger-automator[bot]

articles/iot-operations/deploy-iot-ops/howto-prepare-cluster.md

@@ -166,6 +166,14 @@ Connect your cluster to Azure Arc so that it can be managed remotely.
 
    To prevent unplanned updates to Azure Arc and the system Arc extensions that Azure IoT Operations uses as dependencies, this command disables auto-upgrade. Instead, [manually upgrade agents](/azure/azure-arc/kubernetes/agent-upgrade#manually-upgrade-agents) as needed.
 
+   >[!IMPORTANT]
+   >If your environment uses a proxy server or Azure Arc Gateway, modify the `az connectedk8s connect` command with your proxy information:
+   >
+   >1. Follow the instructions in either [Connect using an outbound proxy server](/azure/azure-arc/kubernetes/quickstart-connect-cluster#connect-using-an-outbound-proxy-server) or [Onboard Kubernetes clusters to Azure Arc with Azure Arc Gateway](/azure/azure-arc/kubernetes/arc-gateway-simplify-networking#onboard-kubernetes-clusters-to-azure-arc-with-your-arc-gateway-resource).
+   >1. Add `169.254.169.254` to the `--proxy-skip-range` parameter of the `az connectedk8s connect` command. [Azure Device Registry](../discover-manage-assets/overview-manage-assets.md#store-assets-as-azure-resources-in-a-centralized-registry) uses this local endpoint to get access tokens for authorization.
+   >
+   >Azure IoT Operations doesn't support proxy servers that require a trusted certificate.
+
 1. Get the cluster's issuer URL.
 
    ```azurecli

articles/iot-operations/deploy-iot-ops/overview-deploy.md

@@ -31,7 +31,8 @@ To install Azure IoT Operations, have the following hardware requirements availa
 
 | Spec | Minimum | Recommended |
 |------|---------|-------------|
-| RAM  | 16-GB   | 32-GB       |
+| Hardware memory capacity (RAM) | 16-GB | 32-GB |
+| Available memory for Azure IoT Operations (RAM) | 10-GB | Depends on usage |
 | CPU  | 4 vCPUs | 8 vCPUs     |
 
 ## Choose your features