Auto labeling cluster resources

[fabriziopandini]

As an operator I would like to have a consistent set of labels for searching cluster resources.

Detailed Description

As the cluster API specification evolves, cluster specification is composed of a growing set of resources e.g. Cluster, AWSCluster, Machine, AWS machine, KubeConfigr, Certificate secrets, Kubeconfig secret etc.

By ensuring everything is part of a cluster consistently labeled it will be possible to simplify the management of a cluster definition and easily implement higher-level tools for deleting/pivoting a cluster

Goals

• Apply a consistent set of labels to all the resources that are part of a cluster (including core objects, provider-specific objects and Kubernetes standard objects like secrets)

Non-Goals

• Apply a consistent set of labels to the cluster API components itself (the manager, CRD definitions etc.)

/kind feature

[prankul88]

@fabriziopandini I can work on this if you like.

[fabriziopandini]

@prankul88 great! let's wait for some more feedback/issue triage before starting though

[joonas]

/assign @fabriziopandini

[fabriziopandini]

In order to simplify for deleting/pivoting, on top of auto labeling, it is necessary also a generic convention for navigating objects and this requires more thinking
So I propose to decrease priority or to close and eventually re-open in future

[ncdc]

Done

[vincepri]

/area clusterctl

[fabriziopandini]

@vincepri considering that clusterctl now relies on the OwnerRef chain (see https://master.cluster-api.sigs.k8s.io/clusterctl/provider-contract.html#ownerreferences-chain), I propose to close this issue.
WDYT?

[vincepri]

/close

[k8s-ci-robot]

@vincepri: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.