|
2 | 2 | title: Configure Hybrid Kubernetes clusters with Azure Monitor for containers | Microsoft Docs
|
3 | 3 | description: This article describes how you can configure Azure Monitor for containers to monitor Kubernetes clusters hosted on Azure Stack or other environment.
|
4 | 4 | ms.topic: conceptual
|
5 |
| -ms.date: 12/04/2019 |
| 5 | +ms.date: 01/24/2020 |
6 | 6 | ---
|
7 | 7 |
|
8 | 8 | # Configure hybrid Kubernetes clusters with Azure Monitor for containers
|
@@ -34,7 +34,7 @@ Before you start, make sure that you have the following:
|
34 | 34 | |*.blob.core.windows.net |Port 443 |
|
35 | 35 | |*.dc.services.visualstudio.com |Port 443 |
|
36 | 36 |
|
37 |
| -* The containerized agent requires `cAdvisor port: 10255` to be opened on all nodes in the cluster to collect performance metrics. |
| 37 | +* The containerized agent requires Kubelet’s `cAdvisor secure port: 10250` or `unsecure port :10255` to be opened on all nodes in the cluster to collect performance metrics. We recommend you configure `secure port: 10250` on the Kubelet’s cAdvisor if it’s not configured already. |
38 | 38 |
|
39 | 39 | * The containerized agent requires the following environmental variables to be specified on the container in order to communicate with the Kubernetes API service within the cluster to collect inventory data - `KUBERNETES_SERVICE_HOST` and `KUBERNETES_PORT_443_TCP_PORT`.
|
40 | 40 |
|
@@ -285,12 +285,12 @@ If you encounter an error while attempting to enable monitoring for your hybrid
|
285 | 285 | * OmsAgent Health service is running
|
286 | 286 | * The Log Analytics workspace Id and key configured on the containerized agent match with the workspace the Insight is configured with.
|
287 | 287 | * Validate all the Linux worker nodes have `kubernetes.io/role=agent` label to schedule rs pod. If it doesn't exist, add it.
|
288 |
| -* Validate `cAdvisor port: 10255` is opened on all nodes in the cluster. |
| 288 | +* Validate `cAdvisor secure port:10250` or `unsecure port: 10255` is opened on all nodes in the cluster. |
289 | 289 |
|
290 | 290 | To execute with Azure PowerShell, use the following commands in the folder that contains the script:
|
291 | 291 |
|
292 | 292 | ```powershell
|
293 |
| -.\TroubleshootError_nonAzureK8s.ps1 - azureLogAnalyticsWorkspaceResourceId </subscriptions/<subscriptionId>/resourceGroups/<resourcegroupName>/providers/Microsoft.OperationalInsights/workspaces/<workspaceName> -kubeConfig <kubeConfigFile> |
| 293 | +.\TroubleshootError_nonAzureK8s.ps1 - azureLogAnalyticsWorkspaceResourceId </subscriptions/<subscriptionId>/resourceGroups/<resourcegroupName>/providers/Microsoft.OperationalInsights/workspaces/<workspaceName> -kubeConfig <kubeConfigFile> -clusterContextInKubeconfig <clusterContext> |
294 | 294 | ```
|
295 | 295 |
|
296 | 296 | ## Next steps
|
|
0 commit comments