Merge pull request #226717 from austonli/patch-30

Proxy support in container insights

Author: prmerger-automator[bot]

articles/aks/http-proxy.md

@@ -126,7 +126,6 @@ The HTTP proxy with the Monitoring add-on supports the following configurations:
 The following configurations aren't supported:
 
   - The Custom Metrics and Recommended Alerts features aren't supported when you use a proxy with trusted certificates
-  - Outbound proxy isn't supported with Azure Monitor Private Link Scope (AMPLS)
 
 ## Next steps
 

articles/azure-monitor/containers/container-insights-agent-config.md

@@ -45,6 +45,12 @@ The following table describes the settings you can configure to control metric c
 
 ConfigMap is a global list and there can be only one ConfigMap applied to the agent. You can't have another ConfigMap overruling the collections.
 
+### Agent settings for outbound proxy with Azure Monitor Private Link Scope (AMPLS)
+
+| Key | Data type | Value | Description |
+|--|--|--|--|
+| `[agent_settings.proxy_config] ignore_proxy_settings =` | Boolean | True or false | Set this value to true to ignore proxy settings. On both AKS & Arc K8s enviornments, if your cluster is configured with forward proxy, then proxy settings are automatically applied and used for the agent. For certain configurations, such as, with AMPLS + Proxy, you may with for the proxy config to be ignored. . By default, this setting is set to `false`. |
+
 ## Configure and deploy ConfigMaps
 
 To configure and deploy your ConfigMap configuration file to your cluster:
@@ -66,6 +72,7 @@ To configure and deploy your ConfigMap configuration file to your cluster:
 
 The configuration change can take a few minutes to finish before taking effect. Then all Azure Monitor Agent pods in the cluster will restart. The restart is a rolling restart for all Azure Monitor Agent pods, so not all of them restart at the same time. When the restarts are finished, a message similar to this example includes the following result: `configmap "container-azm-ms-agentconfig" created`.
 
+
 ## Verify configuration
 
 To verify the configuration was successfully applied to a cluster, use the following command to review the logs from an agent pod: `kubectl logs ama-logs-fdf58 -n kube-system`. If there are configuration errors from the Azure Monitor Agent pods, the output will show errors similar to the following example: