-
Notifications
You must be signed in to change notification settings - Fork 41.6k
[FG:InPlacePodVerticalScaling] Fix AllocatedResources feature gate annotation #128687
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
Conversation
|
/triage accepted |
|
/assign @thockin |
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.
Thanks!
/lgtm
/approve
|
LGTM label has been added. Git tree hash: 3bcc7d1f64f9bdaeffa1a78424ce59cfadc7d627
|
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: tallclair, thockin 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 |
|
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. |
|
/test pull-kubernetes-node-e2e-containerd |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
The feature gate guarding the
AllocatedResourcesfield changed in #128377, but I forgot to update the annotation on the field.Special notes for your reviewer:
Technically this field is guarded by both
InPlacePodVerticalScalingandInPlacePodVerticalScalingAllocatedStatus. Should I put both on the field? Like this:Does this PR introduce a user-facing change?
/sig node
/milestone v1.32
/priority important-soon