Skip to content

Commit 55e5999

Browse files
committed
add info
1 parent 0a321ba commit 55e5999

File tree

3 files changed

+28
-3
lines changed

3 files changed

+28
-3
lines changed

articles/azure-arc/kubernetes/conceptual-cluster-connect.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,11 @@
11
---
2-
title: "Access Azure Arc-enabled Kubernetes clusters from anywhere using cluster connect"
2+
title: "Cluster connect access to Azure Arc-enabled Kubernetes clusters"
33
ms.date: 07/22/2022
44
ms.topic: conceptual
55
description: "Cluster connect allows developers to access their Azure Arc-enabled Kubernetes clusters from anywhere for interactive development and debugging."
66
---
77

8-
# Access Azure Arc-enabled Kubernetes clusters from anywhere using cluster connect
8+
# Cluster connect access to Azure Arc-enabled Kubernetes clusters
99

1010
The Azure Arc-enabled Kubernetes *cluster connect* feature provides connectivity to the `apiserver` of the cluster without requiring any inbound port to be enabled on the firewall. A reverse proxy agent running on the cluster can securely start a session with the Azure Arc service in an outbound manner.
1111

articles/azure-arc/kubernetes/identity-access-overview.md

Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,31 @@ description: "Understand identity and access options for Arc-enabled Kubernetes
88

99
# Azure Arc-enabled Kubernetes identity and access overview
1010

11+
You can authenticate, authorize, secure, and control access to your Azure Arc-enabled Kubernetes clusters. Kubernetes role-based access control (Kubernetes RBAC) lets you grant users, groups, and service accounts access to only the resources they need. You can further enhance the security and permissions structure using Azure Active Directory and Azure role-based access control (RBAC).
12+
13+
While Kubernetes RBAC works only on Kubernetes resources within your cluster, Azure RBAC works on resources across your Azure subscription.
14+
15+
This topic provides an overview of these two RBAC systems and how you can use them with your Arc-enabled Kubernetes clusters.
16+
17+
## Kubernetes RBAC
18+
19+
[Kubernetes RBAC](https://kubernetes.io/docs/reference/access-authn-authz/rbac/) provides granular filtering of user actions. With Kubernetes RBAC, You assign users or groups permission to create and modify resources or view logs from running application workloads. You can create roles to define permissions, and then assign those roles to users with role bindings. Permissions may be scoped to a single namespace or across the entire cluster.
20+
21+
The Azure Arc-enabled Kubernetes cluster connect feature uses Kubernetes RBAC to provides connectivity to the `apiserver` of the cluster. This connectivity doesn't require any inbound port to be enabled on the firewall. A reverse proxy agent running on the cluster can securely start a session with the Azure Arc service in an outbound manner. Using the cluster connect feature helps enable interactive debugging and troubleshooting scenarios. It can also be used to provide cluster access to Azure services for [custom locations](conceptual-custom-locations.md).
22+
23+
For more information, see [Cluster connect access to Azure Arc-enabled Kubernetes clusters](conceptual-cluster-connect.md) and [Use cluster connect to securely connect to Azure Arc-enabled Kubernetes clusters](cluster-connect.md).
24+
25+
## Azure RBAC
26+
27+
[Azure role-based access control (RBAC)](/azure/role-based-access-control/overview) is an authorization system built on Azure Resource Manager and Azure Active Directory (Azure AD) that provides fine-grained access management of Azure resources.
28+
29+
With Azure RBAC, role definitions outlines the permissions to be applied. You assign these roles to users or groups via a role assignment for a particular scope. The scope can be across the entire subscription or limited to a resource group or to an individual resource such as a Kubernetes cluster.
30+
31+
Using Azure RBAC with your Arc-enabled Kubernetes clusters allows the benefits of Azure role assignments, such as activity logs showing all Azure RBAC changes to an Azure resource.
32+
33+
For more information, see [Azure RBAC on Azure Arc-enabled Kubernetes](conceptual-azure-rbac.md) and [Use Azure RBAC for Azure Arc-enabled Kubernetes clusters](azure-rbac.md).
1134

1235
## Next steps
1336

37+
- Learn about [access and identity options for Azure Kubernetes Service (AKS) clusters](/azure/aks/concepts-identity).
38+
- - Deploy and manage [cluster extensions](extensions.md).

articles/azure-arc/kubernetes/toc.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@
3636
items:
3737
- name: Identity and access overview
3838
href: identity-access-overview.md
39-
- name: Access cluster from anywhere
39+
- name: Cluster connect access
4040
displayName: connect
4141
href: conceptual-cluster-connect.md
4242
- name: Azure RBAC integration

0 commit comments

Comments
 (0)