Skip to content
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

Closed
sbueringer opened this issue Aug 7, 2023 · 7 comments
Closed

Make ClusterClass generated object names consistent #9135

sbueringer opened this issue Aug 7, 2023 · 7 comments
Assignees
Labels
area/clusterclass Issues or PRs related to clusterclass triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@sbueringer
Copy link
Member

sbueringer commented Aug 7, 2023

Today we have various different naming conventions for objects generated by the topology controller:

  • CP/MHC: {cluster-name}-{random-suffix}
  • CP: InfraMachineTemplate {cluster-name}-control-plane-{random-suffix}
  • MD/MHC: {cluster-name}-{topology-name}-{random-suffix}
  • MD: BootstrapConfigTemplate: {cluster-name}-{topology-name}-bootstrap-{random-suffix}
  • MD: InfraMachineTemplate: {cluster-name}-{topology-name}-infra-{random-suffix}
  • MP: InfraMachinePool: {cluster-name}-{topology-name}-infra-{random-suffix}

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:

  • CP/MHC: {cluster-name}-{random-suffix}
  • CP: InfraMachineTemplate {cluster-name}-{random-suffix}. (changed)
  • MD/MHC: {cluster-name}-{topology-name}-{random-suffix}
  • MD: BootstrapConfigTemplate: {cluster-name}-{topology-name}-{random-suffix} (changed)
  • MD: InfraMachineTemplate: {cluster-name}-{topology-name}-{random-suffix} (changed)
  • MP: InfraMachinePool: {cluster-name}-{topology-name}-{random-suffix} (changed)

Note: This will also make the names in general shorter which will avoid that the names are getting hashed.

@sbueringer sbueringer added the area/clusterclass Issues or PRs related to clusterclass label Aug 7, 2023
@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Aug 7, 2023
@sbueringer
Copy link
Member Author

@sbueringer
Copy link
Member Author

/triage accepted

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Aug 7, 2023
@fabriziopandini
Copy link
Member

+1 for me!

@chrischdi
Copy link
Member

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 👍

@sbueringer
Copy link
Member Author

Highlighted the delta above with: (changed)

@sbueringer
Copy link
Member Author

/close

all PRs merged

@k8s-ci-robot
Copy link
Contributor

@sbueringer: Closing this issue.

In response to this:

/close

all PRs merged

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/clusterclass Issues or PRs related to clusterclass triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

4 participants