Skip to content

Commit cdc4cec

Browse files
Merge pull request #247317 from JnHs/jh-arck8-portalacc
Add role info in prereqs + general review
2 parents bc913e1 + 90fad75 commit cdc4cec

File tree

4 files changed

+25
-9
lines changed

4 files changed

+25
-9
lines changed

articles/azure-arc/kubernetes/kubernetes-resource-view.md

Lines changed: 23 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Access Kubernetes resources from Azure portal
3-
ms.date: 07/22/2022
3+
ms.date: 08/07/2023
44
ms.topic: how-to
55
description: Learn how to interact with Kubernetes resources to manage an Azure Arc-enabled Kubernetes cluster from the Azure portal.
66
---
@@ -13,7 +13,21 @@ The Azure portal includes a Kubernetes resource view for easy access to the Kube
1313

1414
- An existing Kubernetes cluster [connected](quickstart-connect-cluster.md) to Azure as an Azure Arc-enabled Kubernetes resource.
1515

16-
- [Service account token](cluster-connect.md#service-account-token-authentication-option) for authentication to the cluster.
16+
- An account that can authenticate to the cluster and access the resources in the portal:
17+
18+
- If using [Azure RBAC](azure-rbac.md), ensure that the Azure Active Directory (Azure AD) account that will access the portal has a role that lets it authenticate to the cluster, such as [Azure Arc Kubernetes Viewer](/azure/role-based-access-control/built-in-roles):
19+
20+
```azurecli
21+
az role assignment create --role "Azure Arc Kubernetes Viewer" --assignee $AAD_ENTITY_OBJECT_ID --scope $ARM_ID_CLUSTER
22+
```
23+
24+
- If using [cluster connect with service account token authentication](cluster-connect.md#service-account-token-authentication-option), ensure that the account uses a Kubernetes cluster role that can authenticate to the cluster, such as `cluster-admin`:
25+
26+
```console
27+
kubectl create clusterrolebinding demo-user-binding --clusterrole cluster-admin --user=$AAD_ENTITY_OBJECT_ID`
28+
```
29+
30+
The same account must have an Azure role such as [Azure Arc Kubernetes Viewer](/azure/role-based-access-control/built-in-roles) in order to authenticate to the Azure portal and view Arc-enabled cluster resources.
1731

1832
## View Kubernetes resources
1933

@@ -25,19 +39,20 @@ To see the Kubernetes resources, navigate to your cluster in the Azure portal. T
2539
- **Storage** shows your Azure storage classes and persistent volume information.
2640
- **Configuration** shows your cluster's config maps and secrets.
2741

28-
[ ![Kubernetes workloads information displayed in the Azure portal](media/kubernetes-resource-view/workloads.png) ](media/kubernetes-resource-view/workloads.png#lightbox)
42+
:::image type="content" source="media/kubernetes-resource-view/workloads.png" alt-text="Screenshot of Kubernetes workloads information in the Azure portal." lightbox="media/kubernetes-resource-view/workloads.png":::
2943

3044
## Edit YAML
3145

3246
The Kubernetes resource view also includes a YAML editor. A built-in YAML editor means you can update Kubernetes objects from within the portal and apply changes immediately.
3347

34-
After you edit the YAML, select **Review + save**, confirm the changes, and then save again.
48+
>[!WARNING]
49+
> The Azure portal Kubernetes management capabilities and the YAML editor are built for learning and flighting new deployments in a development and test setting. Performing direct production changes by editing the YAML is not recommended. For production environments, consider using [GitOps to apply configurations](tutorial-use-gitops-flux2.md).
3550
36-
[ ![YAML editor for Kubernetes objects displayed in the Azure portal](media/kubernetes-resource-view/yaml-editor.png) ](media/kubernetes-resource-view/yaml-editor.png#lightbox)
51+
After you edit the YAML, select **Review + save**, confirm the changes, and then save again.
3752

38-
>[!WARNING]
39-
> The Azure portal Kubernetes management capabilities and the YAML editor are built for learning and flighting new deployments in a development and testing setting. Performing direct production changes via UI or CLI is not recommended. For production environments, consider using [Configurations (GitOps)](tutorial-use-gitops-flux2.md).
53+
:::image type="content" source="media/kubernetes-resource-view/yaml-editor.png" alt-text="Screenshot showing the YAML editor for Kubernetes objects displayed in the Azure portal." lightbox="media/kubernetes-resource-view/yaml-editor.png":::
4054

4155
## Next steps
4256

43-
Azure Monitor for containers provides more in-depth information about nodes and containers of the cluster when compared to the Kubernetes resource view described in this article. Learn how to [deploy Azure Monitor for containers](../../azure-monitor/containers/container-insights-enable-arc-enabled-clusters.md?toc=/azure/azure-arc/kubernetes/toc.json) on your cluster.
57+
- Learn how to [deploy Azure Monitor for containers](../../azure-monitor/containers/container-insights-enable-arc-enabled-clusters.md?toc=/azure/azure-arc/kubernetes/toc.json) for more in-depth information about nodes and containers on your clusters.
58+
- Learn about [identity and access options for Azure Arc-enabled Kubernetes](identity-access-overview.md).
-140 KB
Loading
-19.5 KB
Loading

articles/azure-arc/kubernetes/toc.yml

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -97,7 +97,8 @@
9797
href: agent-upgrade.md
9898
- name: Use Private Link Scope
9999
href: private-link.md
100-
- name: Azure portal Kubernetes resource view
100+
- name: View resources in Azure portal
101+
displayName: kubernetes, yaml, workload
101102
href: kubernetes-resource-view.md
102103
- name: Deploy applications consistently
103104
displayName: GitOps, flux, configuration, policy

0 commit comments

Comments
 (0)