-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Auto labeling cluster resources #1489
Comments
@fabriziopandini I can work on this if you like. |
@prankul88 great! let's wait for some more feedback/issue triage before starting though |
/assign @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 |
Done |
/area clusterctl |
@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. |
/close |
@vincepri: Closing this issue. In response to this:
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. |
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
Non-Goals
/kind feature
The text was updated successfully, but these errors were encountered: