You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-monitor/containers/container-insights-livedata-setup.md
+5-3Lines changed: 5 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ ms.reviewer: aul
9
9
10
10
# Configure Live Data in Container insights
11
11
12
-
To view Live Data with Container insights from Azure Kubernetes Service (AKS) clusters, configure authentication to grant permission to access your Kubernetes data. This security configuration allows real-time access to your data through the Kubernetes API directly in the Azure portal.
12
+
To view live data with Container insights from Azure Kubernetes Service (AKS) clusters, configure authentication to grant permission to access your Kubernetes data. This security configuration allows real-time access to your data through the Kubernetes API directly in the Azure portal.
13
13
14
14
This feature supports the following methods to control access to logs, events, and metrics:
15
15
@@ -32,9 +32,11 @@ The Live Data feature uses the Kubernetes API, which is identical to the `kubect
32
32
The Azure portal prompts you to validate your sign-in credentials for an Azure AD cluster. It redirects you to the client registration setup during cluster creation (and reconfigured in this article). This behavior is similar to the authentication process required by `kubectl`.
33
33
34
34
>[!NOTE]
35
-
>Authorization to your cluster is managed by Kubernetes and the security model it's configured with. Users who access this feature require permission to download the Kubernetes configuration (*kubeconfig*), which is similar to running `az aks get-credentials -n {your cluster name} -g {your resource group}`. This configuration file contains the authorization and authentication token for the *Azure Kubernetes Service Cluster User Role*, in the case of Azure RBAC enabled and AKS clusters without Kubernetes RBAC authorization enabled. It contains information about Azure AD and client registration details when AKS is enabled with Azure AD SAML-based single sign-on.
35
+
>Authorization to your cluster is managed by Kubernetes and the security model it's configured with. Users who access this feature require permission to download the Kubernetes configuration (*kubeconfig*), which is similar to running `az aks get-credentials -n {your cluster name} -g {your resource group}`.
36
+
>
37
+
>This configuration file contains the authorization and authentication token for the *Azure Kubernetes Service Cluster User Role*, in the case of Azure RBAC enabled and AKS clusters without Kubernetes RBAC authorization enabled. It contains information about Azure AD and client registration details when AKS is enabled with Azure AD SAML-based single sign-on.
36
38
37
-
Users of this feature require the [Azure Kubernetes Cluster User Role](../../role-based-access-control/built-in-roles.md)access to the cluster to download the `kubeconfig` and use this feature. Users do *not* require contributor access to the cluster to use this feature.
39
+
Users of this feature require the [Azure Kubernetes Cluster User Role](../../role-based-access-control/built-in-roles.md)to access the cluster to download the `kubeconfig` and use this feature. Users do *not* require contributor access to the cluster to use this feature.
38
40
39
41
## Use clusterMonitoringUser with Kubernetes RBAC-enabled clusters
Copy file name to clipboardExpand all lines: articles/azure-monitor/faq.yml
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -1095,7 +1095,7 @@ sections:
1095
1095
- question: |
1096
1096
How do I resolve Azure AD errors when I enable live logs?
1097
1097
answer: |
1098
-
You may see the following error: **The reply url specified in the request does not match the reply urls configured for the application: '<application ID\>'**. The solution to solve it can be found in the article [How to view container data in real time with Container insights](containers/container-insights-livedata-setup.md#configure-ad-integrated-authentication).
1098
+
You may see the following error: **The reply url specified in the request does not match the reply urls configured for the application: '<application ID\>'**. The solution to solve it can be found in the article [How to view container data in real time with Container insights](containers/container-insights-livedata-setup.md#configure-azure-ad-integrated-authentication).
0 commit comments