KEP 5554: In place update pod resources alongside static cpu manager policy KEP creation #5555
+1,266
−0
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,3 @@ | ||
| kep-number: 5554 | ||
| alpha: | ||
| approver: "TBD" | ||
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,53 @@ | ||
| title: In-place Update Pod Resources alognside Static CPU Manager Policy | ||
| kep-number: 5554 | ||
| authors: | ||
| - "@esotsal" | ||
| owning-sig: sig-node | ||
| participating-sigs: | ||
| - sig-node | ||
| status: provisional | ||
|
There was a problem hiding this comment. nit: I would prefer to start off with "implementable" and just get this ready for alpha implementation in this PR since we have already been through a lot of discussion |
||
| creation-date: 2025-09-21 | ||
| reviewers: | ||
| - "@pravk03" | ||
| - "@ffromani" | ||
| - "@tallclair" | ||
| - "@natasha41575" | ||
| - "@dchen1107" | ||
| - "@SergeyKanzhelev" | ||
| - "@jeremyrickard" | ||
| approvers: | ||
| - "@dawnchen" # SIG Node approval | ||
| - "@ffromani" | ||
| - "@tallclair" | ||
|
|
||
| see-also: | ||
| - "keps/sig-node/1287-in-place-update-pod-resources" | ||
| - "keps/sig-node/3570-cpu-manager" | ||
| - "keps/sig-node/5328-node-declared-features" | ||
| replaces: | ||
|
|
||
| # The target maturity stage in the current dev cycle for this KEP. | ||
| stage: alpha | ||
|
|
||
| # The most recent milestone for which work toward delivery of this KEP has been | ||
| # done. This can be the current (upcoming) milestone, if it is being actively | ||
| # worked on. | ||
| latest-milestone: "v1.35" | ||
|
|
||
| # The milestone at which this feature was, or is targeted to be, at each stage. | ||
| milestone: | ||
| alpha: "v1.35" | ||
| beta: "v1.36" | ||
| stable: "v1.37" | ||
|
|
||
| # The following PRR answers are required at alpha release | ||
| # List the feature gate name and the components for which it must be enabled | ||
| feature-gates: | ||
| - name: InPlacePodVerticalScalingExclusiveCPUs | ||
| components: | ||
| - kubelet | ||
| disable-supported: true | ||
|
|
||
| # The following PRR answers are required at beta release | ||
| metrics: | ||
| - TBD | ||
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 you need to put a name and let the PRR team rebalance. Let's check if this is sufficient to make sure the PRR team is aware of this KEP; if so, we can surely keep TBD
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.
I believe the official guidance from the PRR team is to put a name down here and assign the PR to that person; they will rebalance if needed