-
Notifications
You must be signed in to change notification settings - Fork 1.4k
🌱 Feature gate for old infra machine naming #10505
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
🌱 Feature gate for old infra machine naming #10505
Conversation
@lentzi90: The label(s) 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. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/area control-plane-kubeadm |
@lentzi90: The label(s) 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. |
/area provider/control-plane-kubeadm |
87898c3
to
7f5bfaa
Compare
// With this feature gate enabled, infra machines will be named based on the infra machine template. | ||
// The new behavior is that they get the same name as the machine. | ||
// | ||
// Deprecated: v1.7. |
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.
Not sure if this makes sense. I wanted to deprecate it right away since the behavior already changed. However, this means the linter complains that we are using it 😓
7f5bfaa
to
f9a0519
Compare
There is a breaking change to the way infra machines are named in v1.7.0. This commit adds a feature gate for getting the old behavior back. It defaults to disabled so the new behavior stays. It is also marked as deprecated so it can be removed in a future minor release. Signed-off-by: Lennart Jern <[email protected]>
f9a0519
to
cc27e0c
Compare
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
/cc @fabriziopandini |
/hold |
Sorry, wrong button 😃 |
Replaced by #10511 that targets release-1.7. This makes more sense since the idea is that this would be temporary and go away in v1.8 |
/reopen |
@lentzi90: Failed to re-open PR: state cannot be changed. The lentzi90/feature-gate-infra-machine-naming branch was force-pushed or recreated. 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-sigs/prow repository. |
What this PR does / why we need it:
There is a breaking change to the way infra machines are named in v1.7.0. This commit adds a feature gate for getting the old behavior back. It defaults to disabled so the new behavior stays. It is also marked as deprecated so it can be removed in a future minor release.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #10463 (not entirely but at least it makes it possible to get the old behavior back for now)
/area control-plane/kubeadm
/area machineset