In the following image, AKS Clusters have been created in the Azure infrastructure.
When imported into Address Manager, an AKS Cluster is represented by a device with the
Kubernetes Clusters device subtype. The supported resources related to AKS
Clusters are Load Balancers and Virtual Machine Scale Sets.
Note: The VMs located within
the Scale Sets are imported as VM devices. The Scale Sets are imported as tags that
link to the respective VMs.
Clicking on the name of a device loads the following additional information.
Tag hierarchy in Address Manager
When AKS data is imported into Address Manager, it is imported as a hierarchy of tags based on the region, cluster, and node group of the AKS data.
The following is the hierarchy of tags that appears in Address Manager:
- Tag Group: named as Azure Kubernetes Service to distinguish AKS data from other resource tags.
- Level 1 tag: named as the resource group name in Azure to distinguish cluster and node group tags from other resource groups.
- Level 2 tag: named as the BlueCat configuration name. Since tags are used across configurations, using the name of the BlueCat configuration avoids data conflict and mismatches when multiple discovery and visibility requests are run against resources on the same Address Manager.
- Level 3 tag: named as the cluster name.
- Level 4 tag: named as the node pool or agent pool name.