-
Notifications
You must be signed in to change notification settings - Fork 40k
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
In-place Pod Vertical Scaling feature #102884
In-place Pod Vertical Scaling feature #102884
Conversation
Hi @vinaykul. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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/test-infra repository. |
/hold |
/assign @vinaykul |
/remove-sig api-machinery |
Potential fix. PTAL: #116271 |
Looking forward to this epic being available....this can be a life saver in these times of cost cutting. Hope companies using k8s use this for their not so modern apps to cut resource cost. Next most exciting one would be the multi dimensional scaling :) |
For the changelog entry, we might prefer to describe the changes in terms of API fields. The API doesn't have fields named I also like to use Markdown in the changelog. Something like (not tech reviewed for accuracy): - Changed the Pod API so that the `resources` defined for a container are mutable for `cpu` and `memory` resources
- Added a `resizePolicy` for containers within a Pod
- Added an `allocatedResources` field within Pod status (reported per Pod)
- Added a `resources` field within Pod status for reporting actual resource allocations
- Extended `status` within the Pod API to report actual state for container resize operations
- Added Windows support for [CRI](https://k8s.io/docs/concepts/architecture/cri/)
`UpdateContainerResources` operations |
niubility and congratulation |
🐮 |
What type of PR is this?
/kind feature
/kind api-change
What this PR does / why we need it:
This PR brings the following changes that mostly implement In-place Pod Vertical Scaling feature:
Which issue(s) this PR fixes: #9043 #110490
xref kubernetes/enhancements#1287
Special notes for your reviewer:
API changes: See: #111946
Scheduler changes: See
231849a
7db339d
Kubelet implementation: See changes in pkg/kubelet
E2E test: test/e2e/node/pod_resize.go
Does this PR introduce a user-facing change? Yes
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:
Jun 26th:
PodStatus.Resize has now been fully implemented. @thockin Please see below. I hope this cuts as as simple signal to the API user (VPA) as to what's going on with resize, so they may choose to take alternative action in the Deferred / Infeasible cases as allowed by their policy.