Cloud

Node Groups: These contain EC2 instances that comprise the nodes. This is the structure assumed for this topic.

Serverless Option (Fargate Profiles): These contain Fargate nodes. Fargate Profiles are shown for visibility purposes but do not have flow support or Map support at this time.

Summary: This tab contains information such as name, ID, cloud, region, category, private and public addresses, and so forth.

Attached Resources: This tab contains information about things like any attached Network Interfaces, Subnets, Security Groups, and so forth. Resources that do not have flow support, such as Fargate profiles, will have information in only the details panel.

Traffic: This tab contains traffic information, much like that shown in the Traffic page, but filtered for the selected luster in this example.

Resource Map: This tab shows the structure comprising the cluster. In this example, assume it shows one node group that contains two nodes (EC2 instances) that are container hosts. However, it could potentially contain many more.

The Map displays only the traffic flowing to and from the AKS, EKS, or GKE cluster as a whole. However, when you open the cluster in the resource map, it expands to reveal the traffic within the cluster. For example, the cluster shows the node groups contained within it. If you further expand a node group in the resource map, it displays the EC2 instances (nodes) within the group. The traffic between these nodes is displayed on the Traffic page. The image shows an example of an EKS cluster.

Additionally, communication between the Kubernetes control plane and its compute instances is reflected as AKS-to-node, EKS-to-node, or GKE-to-node traffic on the Traffic page.