CDV also imports additional IP networks that are used by Kubernetes pods. Pods from
different Kubernetes nodes might use the same IP. A node's IP address will not be
linked, but the IP address will still be shown in the CLUSTER_IP
UDF.
When CDV imports internal Kubernetes resources (pods and services), it creates separate Configurations for each Kubernetes cluster and imports each cluster's resources the appropriate Configuration. These Configurations are distinct from standard and overlapping Configurations.
CDV updates internal AKS resources as follows:
-
During Discovery jobs, CDV updates the list of pods and services within an EKS Cluster.
-
During Visibility jobs, CDV updates pods and services only when related nodes are updated, due to limitations of the Azure Event Grid.
Within BAM, clicking a device displays imported information about the device and other details:
AKS tag hierarchy in Address Manager
CDV imports AKS information into Address Manager as a Tag Group with a hierarchy based on the region, cluster, and node group of the originating AKS data. All imported resources are tagged so that they appear within the appropriate nodepool and cluster.
This hierarchy uses the following template:
Tag Group: Always named
Azure Kubernetes Service.Level 1 tag name: The resource group name from Azure.
Level 2 tag name: The BlueCat configuration name.
Level 3 tag name: The cluster name.
Level 4 tag: The node pool name or agent pool name.
The same tags for clusters, node pools, and agent pools are often used across multiple configurations. This hierarchy helps distinguish similarly-named tags in different configurations from each other.
For example, the tag resource for an agent pool with the name agentpool
in the cluster test_cni, that's part of the configuration
demo/eng-sandbox-cloud-integration-test in the resource group n-test would
appear as follows:
Internal Kubernetes resources
Internal Kubernetes resources appear as follows in BAM: