Tagging resources is not a new idea and it is widely used across cloud/service providers, that allow the operators to use tags to better identify deployed business resources. Today, this is not available, making it harder to create processes that allow operators to identify deployed resources, in particular deployed clusters. Leading operators to use the cluster name or project name to build strict hierarchies, to distinguish, as an example, which projects or clusters are development or production by providing a prefix or suffix. This approach is brittle, since you cannot change the name of a cluster (or want to) needing to come up with client side mapping rules to better manage the deployed clusters. Tagging project clusters allows operators to qualify and/or better identify the deployed resources, expanding their capabilities to build business logic process for resources management. These tags should be exposed via API calls, such as GetOneCluster.