AWS Elastic Kubernetes Service (EKS) data - Adaptive Applications - BlueCat Gateway - 23.3.2

Cloud Discovery & Visibility Administration Guide

Product name
BlueCat Gateway

Cloud Discovery & Visibility imports two components of EKS: cluster and node group data.


In the following image, EKS clusters have been created in the AWS infrastructure.

When imported into Address Manager, an EKS cluster is represented by a device with the Kubernetes Clusters device subtype.

Within the AWS infrastructure, each EKS cluster is registered with a VPC. To represent this relationship in Address Manager, a tag is created with the same name as the EKS Cluster Device and linked to the corresponding address space.

Node group

In the following image, node groups have been added to an existing EKS cluster in the AWS infrastructure.

When imported into Address Manager, an EKS node group is represented by a tag. The node group tag is added to the associated EKS cluster device.

Within the AWS infrastructure, a node group manages one or many EC2 instances. If you enable the discovery of EC2 instances, node groups tagged to the EC2 instance device are also imported

Tag hierarchy in Address Manager

When EKS data is imported into Address Manager, it is imported as a hierarchy of tags based on the region, cluster, and node group of the EKS data. The following is the hierarchy of tags that appears in Address Manager:
  • Tag Group: named as AWS Elastic Kubernetes Service to distinguish EKS data from other resource tags.
  • Level 1 tag: named as the discovered Region name in AWS to distinguish cluster and node group tags from other regions.
  • 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 EKS cluster name.
  • Level 4 tag: named as the EKS node group name.