-
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
Make ClusterClass generated object names consistent #9135
Comments
cc @fabriziopandini @vincepri @killianmuldoon @chrischdi /assign |
/triage accepted |
+1 for me! |
Note: the changes only affect the BootstrapConfigTemplate and InfraMachineTemplates so it also does not affect any machine later on and should be safe from that perspective 👍 |
Highlighted the delta above with: (changed) |
/close all PRs merged |
@sbueringer: 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. |
Today we have various different naming conventions for objects generated by the topology controller:
I would suggest to simplify them and thus make them consistent. I think there is no need to put a bootstrap or infra string in the name of a BootstrapConfigTemplate / InfrastructureMachineTemplate (basically this is just repeating the type in the name)
I would suggest:
Note: This will also make the names in general shorter which will avoid that the names are getting hashed.
The text was updated successfully, but these errors were encountered: