-
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 #9254
🌱 Make ClusterClass generated object names consistent #9254
Conversation
/test pull-cluster-api-e2e-full-main |
Signed-off-by: Stefan Büringer buringerst@vmware.com
2706f3a
to
7bc1644
Compare
Just a question, if we directly modify the name, will there be any compatibility issues? Not long ago, I also wanted to pick up this issue. However, I made the same modification but did not submit a pull request in the end because I was unsure if this modification would cause any compatibility issues. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/area clusterclass
There should be no compatibility issue. Do you mean during upgrades? We only use those functions when we create the name of new objects. So existing objects are not affected in any way by this change. Otherwise they would be already affected today as we always add a random suffix to the names :) (so the full name will be different in every reconcile anyway) |
/test pull-cluster-api-e2e-full-main |
clusterctl upgrade is green and checked the test artifacts. Everything looks as expected |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
LGTM label has been added. Git tree hash: 1d84a5d87af30d648393a28b6337c38b1a19e8fb
|
/lgtm |
/approve /hold (Feel free to unhold whenever you'd like) |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: killianmuldoon The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/hold cancel |
Signed-off-by: Stefan Büringer buringerst@vmware.com
What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Part of #9135