marians
commented
6 months ago To support platform teams managing lots of clusters, I would like to set a focus on providing a much richer clusters list. In addition to that, some information may only be accessible on a per-cluster basis. But here I want to propose some items and functions for the tabular list.
-
Annotations and labels on the
cluster.x-k8s.ioCluster resource. Some of them are defined by Giant Swarm for a purpose we know (example: scheduled upgrade), some are defined by the customer. We could offer one table column per annotation key and per label key. As this would make the table overly wide, so these columns would have to be hidden by default and custom column selection would be offered. -
Grouping the cluster overview by a user-defined column. For example, a customer uses labels like
acme/environment: productionon a cluster. This way the list can be grouped by environment production/development/staging. -
Filtering by columns. It should be easy to select a certain field and only show items with a certain value (or matching a pattern)
-
Additional details to show in columns, not necessarily from the main cluster resource. We might need ways to pull this from non Kubernetes sources, e. g. Prometheus, in a non-blocking way.
- Kubernetes version
- Number of worker nodes
- CPU
- RAM
As a cluster admin, I want to use Backstage to