KOP Cluster Metadata - Cluster Labels - Rafay Product Documentation

Cluster Labels

Infrastructure Administrators can optionally "assign" custom labels to their managed clusters during cluster import or provisioning. Cluster labels can then be used to power "fleet" workflows including sophisticated workload placement policies or Kubernetes Upgrades.


Default Cluster Labels

Every managed cluster (imported or provisioned) comes with a number of "default" cluster labels. These can be used by customers, but cannot be deleted or updated.

Note: Any label with a "rafay.dev/*" prefix is a default cluster label.

Note: For cluster overrides, use customer-managed custom labels instead of Rafay default labels (which start with rafay.dev/clusterName). Defining your own labels ensures consistent and reliable selection of clusters for overrides.


Add/Remove Labels For A Cluster

Custom cluster labels can be added or removed in the cluster configuration:

Explore our blog for deeper insights on Auto Inject Project Name in Cluster Labels, available here!


Cluster Label Management

Alternately, Infrastructure Administrators can also manage the custom labels for multiple clusters:


View Cluster Labels


Filter by Labels

The Web Console provides administrators the ability to filter and view the list of clusters by "cluster labels".

An illustrative example shown below