| Info |
|---|
The article explains how to provide access to AKS Cluster with enabled Active Directory(AD) integration for Cloudaware to discover AKS resources automatically. If your AKS cluster is not AD-managed, grant Cloudaware the permission Microsoft.ContainerService/managedClusters/listClusterUserCredential/read as described here. |
If Active Directory(AD) integration is enabled for AKS cluster, Azure allows access to AKS cluster resources (pods, nodes, etc) automatically using authorization via AD.
Set up the cluster role binding in AKS cluster for the Azure Application that has been added into Cloudaware.
Access Setup
1. Locate the service principal ID of the Azure Application added to Cloudaware:
...
Select the application (in this example, cloudaware-api-access) → Overview. Copy and save the Object ID which is the unique ID of the service principal object associated with this application.
...
32. In your AKS cluster create cloudaware-rbac.yaml using the section below:
...
<SERVICE-PRINCIPAL-OBJECT-ID> insubjects is a placeholder that needs to be replaced by your Azure Application Object ID.
43. Run the following command:
| Code Block |
|---|
kubectl create -f cloudaware-rbac.yaml |
Further Configuration
| Note |
|---|
If your Amazon EKS Cluster is running in a private network, check this guide to install Cloudaware Breeze agent for secure connection. |
Please allow up to 24 hours for the AKS resources to be collected and displayed in Cloudaware CMDB.
List of AKS Cluster Objects
Cloudaware supports the following AKS cluster objects:
...