Skip to content

KEP 6030: Dynamic Resize of Memory-Backed Volumes [alpha]#6050

Open
natasha41575 wants to merge 1 commit intokubernetes:masterfrom
natasha41575:resize_mem_volumes
Open

KEP 6030: Dynamic Resize of Memory-Backed Volumes [alpha]#6050
natasha41575 wants to merge 1 commit intokubernetes:masterfrom
natasha41575:resize_mem_volumes

Conversation

@natasha41575
Copy link
Copy Markdown
Contributor

@natasha41575 natasha41575 commented Apr 30, 2026

New KEP for Dynamic Resize of Memory-Backed Volumes (alpha targeting 1.37)

Issue link: #6030

This KEP proposes extending the In-Place Pod Vertical Scaling infrastructure to support dynamic resizing of memory-backed emptyDir volumes without pod disruption.

A working proof-of-concept implementation based on the proposed design can be found at kubernetes/kubernetes#138301. The goal of the PoC is to demonstrate the simplicity and feasibility.

Antigravity was used to help with research and writing. However:

  • I thoroughly reviewed / fact-checked all claims made by AI to the best of my ability, including running manual tests, combing through the codebase, cross-checking documentation, and prototyping code changes to ensure technical feasibility.
  • All design ideas came from humans.

@k8s-ci-robot k8s-ci-robot added the kind/kep Categorizes KEP tracking issues and PRs modifying the KEP directory label Apr 30, 2026
@k8s-ci-robot k8s-ci-robot added the sig/node Categorizes an issue or PR as relevant to SIG Node. label Apr 30, 2026
@k8s-ci-robot
Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: natasha41575
Once this PR has been reviewed and has the lgtm label, please assign dchen1107, deads2k for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details 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 size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Apr 30, 2026
@natasha41575
Copy link
Copy Markdown
Contributor Author

/assign @tallclair @ndixita @msau42 @jsafrane
/cc @SergeyKanzhelev @haircommander @xing-yang @saad-ali

/sig node
/sig storage

@k8s-ci-robot k8s-ci-robot added the sig/storage Categorizes an issue or PR as relevant to SIG Storage. label Apr 30, 2026
@natasha41575 natasha41575 force-pushed the resize_mem_volumes branch 3 times, most recently from 53bb310 to 204aa19 Compare May 1, 2026 15:20
@natasha41575 natasha41575 force-pushed the resize_mem_volumes branch from 204aa19 to 28a8a3e Compare May 1, 2026 16:11
@k8s-ci-robot
Copy link
Copy Markdown
Contributor

@natasha41575: The following tests 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-enhancements-test 28a8a3e link true /test pull-enhancements-test
pull-enhancements-verify 28a8a3e link true /test pull-enhancements-verify

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.

Details

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.

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

Labels

cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/kep Categorizes KEP tracking issues and PRs modifying the KEP directory sig/node Categorizes an issue or PR as relevant to SIG Node. sig/storage Categorizes an issue or PR as relevant to SIG Storage. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants