Documentation updates for Pod Level In Place resize alpha #52928
Conversation
k8s-ci-robot
added
cncf-cla: yes
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Hi @ndixita , since this is for the 1.35 release, please could you open it against the 1.35-dev branch? cc: @kubernetes/release-team-docs |
|
/sig node |
k8s-ci-robot
added
sig/node
github-project-automation
bot
moved this to Triage
in SIG Node: code and documentation PRs
k8s-ci-robot
added
the
do-not-merge/work-in-progress
k8s-ci-robot
added
size/XXL
|
189 commits? We shouldn't merge but as is. until the number is much lower |
k8s-ci-robot
added
the
do-not-merge/hold
|
Hello @ndixita 👋, v1.35 Docs Team here again! We are closing in on the deadline to get your PR ready for review before Tuesday 18th November 2025, so I'm sending a second reminder. Please take a look at the Documenting for a release - PR Ready for Review document to get your PR ready for review before the deadline. Please also let us know once your PR is fully Ready for Review -- meaning all documentation updates are complete and it's awaiting reviewer feedback -- so we can update our tracking. Thank you! |
ndixita
force-pushed
the
plr-ippr-docs
branch
from
ef5263e to
55adebc
Compare
👷 Deploy Preview for kubernetes-io-vnext-staging processing.
|
|
[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 |
k8s-ci-robot
added
size/L
ndixita
changed the title
|
@Jimmykhangnguyen PR is ready for review |
|
/cc @tallclair |
…ple for alpha stage of InPlacePodLevelResourcesVerticalScaling feature Signed-off-by: ndixita <ndixita@google.com>
ndixita
force-pushed
the
plr-ippr-docs
branch
from
55adebc to
7bedc9b
Compare
|
|
||
| The In-place Pod Resize feature allows modifying resource allocations for a running Pod, avoiding application disruption. The process for resizing individual container resources is covered in the documentation [Resize CPU and Memory Resources assigned to Containers](/docs/tasks/configure-pod-container/resize-container-resources.md). | ||
|
|
||
| This document focuses on the new capability introduced in Kubernetes v1.35: In-place |
There was a problem hiding this comment.
| This document focuses on the new capability introduced in Kubernetes v1.35: In-place | |
| This document focuses on the In-place |
do not mention versions. It will be easier to promote the documentation later. Version is already auto-generated by FG tag above
|
|
||
| {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}} | ||
|
|
||
| Your Kubernetes server must be at or later than version 1.35. |
There was a problem hiding this comment.
you already have a version check above. This is how it looks rendered:
| @@ -0,0 +1,160 @@ | |||
| --- | |||
| title: Resize CPU and Memory Resources assigned to Containers | |||
There was a problem hiding this comment.
I am not sure why it doesn't show up in left pane, maybe some index needs to be updated as well:
|
|
||
| The following [feature | ||
| gates](/docs/reference/command-line-tools-reference/feature-gates/) must be enabled | ||
| for your control plane and for all nodes in your cluster: |
There was a problem hiding this comment.
do we need declared features as well?
|
|
||
| * Retry Priority: Deferred resizes are retried based on PriorityClass, then QoS class (Guaranteed over Burstable), and finally by the duration they have been deferred. | ||
|
|
||
| * Tracking: You can use the observedGeneration fields to track which Pod specification (metadata.generation) corresponds to the status of the latest processed resize request. |
There was a problem hiding this comment.
| * Tracking: You can use the observedGeneration fields to track which Pod specification (metadata.generation) corresponds to the status of the latest processed resize request. | |
| * Tracking: You can use the `observedGeneration` fields to track which Pod specification (metadata.generation) corresponds to the status of the latest processed resize request. |
| the sum of container limits is permitted to exceed the Pod-level limit, enabling | ||
| resource sharing across containers within the Pod. | ||
|
|
||
| ## Example: Resizing Pod-Level Resources |
There was a problem hiding this comment.
it will be nice to give example of failed resize as part of this task page
| defaultValue: false | ||
| fromVersion: "1.35" | ||
| --- | ||
| Enables in-place pod-level resources vertical scaling. |
There was a problem hiding this comment.
Maybe link to the task page. The sentence by itself is hard to parse to somebody who is not super expert in k8s
6 participants
Description
Adding documentation for InPlacePodLevelResourcesVerticalScaling feature alpha stage.
Issue: kubernetes/enhancements#5419