What would you like to be added?
Currently, when viewing the Nodes list in Freelens, it is difficult to quickly identify which managed Node Group or Node Pool a specific node belongs to without clicking into the node details and inspecting its labels.
As a cluster administrator managing environments on cloud providers (like AWS EKS, GCP GKE, or Azure AKS), nodes are frequently organized into distinct node groups. Having visibility into this directly from the list view would significantly improve cluster management, troubleshooting, and upgrade planning.
Why is this needed?
Managing Kubernetes clusters on cloud providers heavily relies on Node Groups or Node Pools to separate different types of workloads (e.g., GPU nodes, high-memory nodes, spot instances).
When an issue occurs, or when planning rolling upgrades/scaling events, administrators need to understand the cluster topology at a glance. Currently, identifying which node belongs to which group requires clicking into each individual node's details and manually scrolling through its labels. This is highly inefficient when managing dozens or hundreds of nodes. Adding a dedicated column allows for immediate visual grouping, faster troubleshooting, and better operational awareness directly from the main list view.
What would you like to be added?
Currently, when viewing the Nodes list in Freelens, it is difficult to quickly identify which managed Node Group or Node Pool a specific node belongs to without clicking into the node details and inspecting its labels.
As a cluster administrator managing environments on cloud providers (like AWS EKS, GCP GKE, or Azure AKS), nodes are frequently organized into distinct node groups. Having visibility into this directly from the list view would significantly improve cluster management, troubleshooting, and upgrade planning.
Why is this needed?
Managing Kubernetes clusters on cloud providers heavily relies on Node Groups or Node Pools to separate different types of workloads (e.g., GPU nodes, high-memory nodes, spot instances).
When an issue occurs, or when planning rolling upgrades/scaling events, administrators need to understand the cluster topology at a glance. Currently, identifying which node belongs to which group requires clicking into each individual node's details and manually scrolling through its labels. This is highly inefficient when managing dozens or hundreds of nodes. Adding a dedicated column allows for immediate visual grouping, faster troubleshooting, and better operational awareness directly from the main list view.