-
Notifications
You must be signed in to change notification settings - Fork 41.5k
DRA: lock to default-on #134452
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
base: master
Are you sure you want to change the base?
DRA: lock to default-on #134452
Conversation
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The 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. |
/sig node |
0ead324
to
ff3fa40
Compare
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: pohly 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 |
This PR may require API review. If so, when the changes are ready, complete the pre-review checklist and request an API review. Status of requested reviews is tracked in the API Review project. |
ff3fa40
to
6b14027
Compare
The core functionality was enabled by default in 1.34 without any issues that would have suggested turning it off, so now we can lock it to on-by-default. Tests which cover disabling the feature must use version emulation.
6b14027
to
5576f0c
Compare
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
The core functionality was enabled by default in 1.34 without any issues that would have suggested turning it off, so now we can lock it to on-by-default.
Which issue(s) this PR is related to:
KEP: kubernetes/enhancements#4381
Special notes for your reviewer:
Does this PR introduce a user-facing change?