Skip to content

Conversation

@esotsal
Copy link
Contributor

@esotsal esotsal commented Oct 23, 2024

What type of PR is this?

What this PR does / why we need it:

We want to introduce a new feature gate to allow resize for guaranteed pods with integer CPU requests on nodes with a static topology policy to unblock development on #127262.

New gate "InPlacePodVerticalScalingExclusiveCPUs" is off by default, but can be enabled to unblock development of Static CPU management alongside InPlacePodVerticalScaling.

Which issue(s) this PR fixes:

Update: Attempt to fix #128068

Special notes for your reviewer:

Does this PR introduce a user-facing change?

- Ensure resizing for Guaranteed pods with integer CPU requests on nodes with static CPU & Memory policy configured is not allowed for the beta release of in-place resize. The feature gate `InPlacePodVerticalScalingExclusiveCPUs` defaults to `false`, but can be enabled to unblock development on ([#127262](https://github.com/kubernetes/kubernetes/issues/127262), [@tallclair](https://github.com/tallclair)) [SIG Node].

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

? Please advise

/sig node
/priority important-soon
/milestone v1.32

@k8s-ci-robot
Copy link
Contributor

@esotsal: You must be a member of the kubernetes/milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your Milestone Maintainers Team and have them propose you as an additional delegate for this responsibility.

In response to this:

What type of PR is this?

What this PR does / why we need it:

We want to introduce a new feature gate to allow resize for guaranteed pods on nodes with a static topology policy to unblock development on #127262.

New gate "AllowResourceResizeInContainerWithExclusiveCPUs" is off by default, but can be enabled to unblock development of Static CPU management alongside InPlacePodVerticalScaling.

Which issue(s) this PR fixes:

For #128068

Special notes for your reviewer:

Does this PR introduce a user-facing change?

- Ensure resizing for Guaranteed pods on nodes with static CPU & Memory policy configured is not allowed for the beta release of in-place resize. The feature gate `AllowResourceResizeInContainerWithExclusiveCPUs` defaults to `false`, but can be enabled to unblock development on ([#127262](https://github.com/kubernetes/kubernetes/issues/127262), [@tallclair](https://github.com/tallclair)) [SIG Node].

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

? Please advice

/sig node
/priority important-soon
/milestone v1.32

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.

@k8s-ci-robot k8s-ci-robot added release-note Denotes a PR that will be considered when it comes time to generate release notes. sig/node Categorizes an issue or PR as relevant to SIG Node. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/needs-kind Indicates a PR lacks a `kind/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Oct 23, 2024
@esotsal esotsal changed the title [:InPlacePodVerticalScaling] WIP: Gate Disallow in-place resize for guaranteed pods on nodes with a static topology policy [FG:InPlacePodVerticalScaling] WIP: Gate Disallow in-place resize for guaranteed pods on nodes with a static topology policy Oct 23, 2024
@k8s-ci-robot k8s-ci-robot added area/release-eng Issues or PRs related to the Release Engineering subproject sig/release Categorizes an issue or PR as relevant to SIG Release. labels Oct 23, 2024
@esotsal
Copy link
Contributor Author

esotsal commented Oct 23, 2024

/assign @tallclair

Copy link
Member

@tallclair tallclair left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for taking this on. I see this is tagged "WIP" so I assume it's still coming, but the feature gate should be implemented in this same PR (I mean rejecting the resize of exclusive CPU pods)

@esotsal
Copy link
Contributor Author

esotsal commented Oct 23, 2024

Thanks for taking this on. I see this is tagged "WIP" so I assume it's still coming, but the feature gate should be implemented in this same PR (I mean rejecting the resize of exclusive CPU pods)

Correct , that’s the plan, plus necessary tests

@esotsal esotsal force-pushed the esotsal/128068 branch 7 times, most recently from 0957e98 to f4b1caa Compare October 26, 2024 22:33
@k8s-ci-robot k8s-ci-robot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. area/kubelet and removed size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Oct 26, 2024
@k8s-ci-robot k8s-ci-robot removed the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Oct 26, 2024
@esotsal esotsal force-pushed the esotsal/128068 branch 2 times, most recently from 2d4a186 to 8b6da25 Compare November 7, 2024 16:52
…atic topology policy

New gate "InPlacePodVerticalScalingExclusiveCPUs" is off by default,
but can be enabled to unblock development of Static CPU management alongside
InPlacePodVerticalScaling.
@k8s-ci-robot k8s-ci-robot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. labels Nov 7, 2024
@esotsal
Copy link
Contributor Author

esotsal commented Nov 7, 2024

/test pull-kubernetes-e2e-inplace-pod-resize-containerd-main-v2
/test pull-kubernetes-node-kubelet-serial-podresize
/test pull-kubernetes-node-kubelet-serial-crio-cgroupv2
/test pull-kubernetes-e2e-gce-cos-alpha-features

@tallclair
Copy link
Member

/triage accepted
/milestone v1.32

@k8s-ci-robot k8s-ci-robot added this to the v1.32 milestone Nov 7, 2024
@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 Nov 7, 2024
@tallclair
Copy link
Member

/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Nov 7, 2024
@k8s-ci-robot
Copy link
Contributor

LGTM label has been added.

Git tree hash: 01b765e067dd4ef4b04c79e8a72433b7b23c62df

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: esotsal, tallclair

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 7, 2024
@k8s-ci-robot
Copy link
Contributor

@esotsal: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
pull-kubernetes-e2e-gce-cos-alpha-features 2d8939c link false /test pull-kubernetes-e2e-gce-cos-alpha-features

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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. I understand the commands that are listed here.

@pacoxu
Copy link
Member

pacoxu commented Nov 8, 2024

/kind feature
/skip

@k8s-ci-robot k8s-ci-robot added kind/feature Categorizes issue or PR as related to a new feature. and removed do-not-merge/needs-kind Indicates a PR lacks a `kind/foo` label and requires one. labels Nov 8, 2024
@wendy-ha18
Copy link
Member

Hi @pacoxu @tallclair
Appreciate all of your efforts with this PR!!
A gentle reminder that the code freeze has started 02:00 UTC Friday November 8th 2024 . Please make sure this has both lgtm and approved labels ASAP, and file an Exception.

@k8s-ci-robot k8s-ci-robot merged commit 81dc453 into kubernetes:master Nov 8, 2024
17 of 18 checks passed
@esotsal esotsal deleted the esotsal/128068 branch November 8, 2024 05:44
@sftim
Copy link
Contributor

sftim commented Nov 11, 2024

Make sure to document InPlacePodVerticalScalingExclusiveCPUs for v1.32
(it's OK to file a k/website issue and delegate; in fact, I recommend it)

@esotsal
Copy link
Contributor Author

esotsal commented Nov 11, 2024

Make sure to document InPlacePodVerticalScalingExclusiveCPUs for v1.32 (it's OK to file a k/website issue and delegate; in fact, I recommend it)

kubernetes/website#48687 created @sftim , thanks !

@esotsal
Copy link
Contributor Author

esotsal commented Jul 28, 2025

Adding for tracking purposes, this PR is related with kubernetes/enhancements#5294

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. area/e2e-test-framework Issues or PRs related to refactoring the kubernetes e2e test framework area/kubelet area/release-eng Issues or PRs related to the Release Engineering subproject area/test cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/feature Categorizes issue or PR as related to a new feature. lgtm "Looks good to me", indicates that a PR is ready to be merged. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. release-note Denotes a PR that will be considered when it comes time to generate release notes. sig/node Categorizes an issue or PR as relevant to SIG Node. sig/release Categorizes an issue or PR as relevant to SIG Release. sig/testing Categorizes an issue or PR as relevant to SIG Testing. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Projects

Archived in project
Archived in project

Development

Successfully merging this pull request may close these issues.

[FG:InPlacePodVerticalScaling] Disable in-place resize for guaranteed pods on nodes with a static topology policy

8 participants