Support to size memory backed volumes

[derekwaynecarr]

Enhancement Description

• Add support to size memory backed volumes
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/1967-size-memory-backed-volumes
• Primary contact (assignee): @derekwaynecarr @kannon92
• Responsible SIGs: sig-node
• Enhancement target (which target equals to which milestone):
  • Alpha release target 1.20
  • Beta release target 1.22
  • Stable release target 1.32
• Alpha
  • KEP (k/enhancements) update PR(s): Size memory backed volumes #1968
  • Code (k/k) update PR(s): Add support to size memory backed volumes kubernetes#94444
  • Docs (k/website) update PR(s): Document SizeMemoryBackedVolumes feature for 1.20 website#24906
• Beta
  • KEP (k/enhancements) update PR(s): Move 1967 Support to size memory backed volumes to Beta #2628
  • Code (k/k) update PR(s): Revert "Revert "Promote SizeMemoryBackedVolumeSizing to beta"" kubernetes#101048
  • Docs (k/website) update(s): Promote size memory backed volumes to beta website#27990
• GA
  • KEP (k/enhancements) update PR(s): KEP-1967: promote size memory backed volumes to stable #4812
  • Code (k/k) update PR(s): KEP-1967: promote size backed memory volumes to stable kubernetes#126981
  • Docs (k/website) update(s): [KEP-1967] - update docs for GA website#48254

[derekwaynecarr]

/sig node

[kikisdeliveryservice]

Hi @derekwaynecarr !

Enhancements Lead here. You've seemed have linked a PR instead of your KEP (https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/1967-size-memory-backed-volumes) I've updated the description to fix.

[kikisdeliveryservice]

Related PR kubernetes/kubernetes#94444

[MorrisLaw]

Hey @derekwaynecarr ,

Another friendly reminder that since this Enhancement is scheduled to be in 1.20, please keep in mind the important upcoming dates:
Friday, Nov 6th: Week 8 - Docs Placeholder PR deadline
Thursday, Nov 12th: Week 9 - Code Freeze

Also, please link all of your k/k PR as well as docs PR to this issue so we can track them.

Thank you,
Jeremy

[annajung]

Hello @derekwaynecarr 👋 , 1.20 Docs lead here.

Does this enhancement work planned for 1.20 require any new docs or modification to existing docs?

If so, please follows the steps here to open a PR against dev-1.20 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Nov 6th

Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.

Thank you!

[annajung]

Hi @derekwaynecarr

The docs placeholder deadline is this Friday. Please make sure to create a placeholder PR against the dev-1.20 branch in the k/website before the deadline

Also, please keep in mind the important upcoming dates:

• Friday, Nov 6th: Week 8 - Docs Placeholder PR deadline
• Thursday, Nov 12th: Week 9 - Code Freeze
• Monday, Nov 23rd: Week 11 - Docs PR Ready for Review

As a reminder, please link all of your k/k PR as well as docs PR to this issue for the release team to track.

[MorrisLaw]

Hi @derekwaynecarr

Just a friendly reminder the code freeze deadline is this Thursday. Please make sure to have any code merged in before the deadline.

Also, please keep in mind the important upcoming dates:

• Thursday, Nov 12th: Week 9 - Code Freeze
• Monday, Nov 23rd: Week 11 - Docs PR Ready for Review

As a reminder, please link all of your k/k PR as well as docs PR to this issue for the release team to track.

[kikisdeliveryservice]

Double checked with Derek and this is completed for code freeze.

[derekwaynecarr]

/milestone v1.21

[mvortizr]

/assign

[arunmk]

Hi @derekwaynecarr, @mvortizr,

Since your Enhancement is scheduled to be in 1.21, please keep in mind the important upcoming dates:

• Tuesday, March 9th: Week 9 - Code Freeze
• Tuesday, March 16th: Week 10 - Docs Placeholder PR deadline
  • If this enhancement requires new docs or modification to existing docs, please follow the steps in the Open a placeholder PR doc to open a PR against k/website repo.

As a reminder, please link all of your k/k PR(s) and k/website PR(s) to this issue so we can track them.

Thanks!

[arunmk]

Hi @derekwaynecarr @mvortizr ,

Enhancements team does not have a linked PR to track for the upcoming code freeze. Could you please link a PR to this KEP so that we may track it.

We are currently marking this KEP as 'At Risk' for the upcoming code freeze on 3/9.

Thanks

[arunmk]

Hi @derekwaynecarr @mvortizr ,

A friendly reminder that Code freeze is 4 days away, March 9th EOD PST

Any enhancements that are NOT code complete by the freeze will be removed from the milestone and will require an exception to be added back.

Please also keep in mind that if this enhancement requires new docs or modification to existing docs, you'll need to follow the steps in the Open a placeholder PR doc to open a PR against k/website repo by March 16th EOD PST

Thanks!

[kannon92]

/assign

Going to take this to stable in 1.32.

[kannon92]

Opened up #4812.

[dipesh-rawat]

Hello @kannon92 👋, v1.32 Enhancements team here.

Just checking in as we approach enhancements freeze on 02:00 UTC Friday 11th October 2024 / 19:00 PDT Thursday 10th October 2024.

This enhancement is targeting for stage stable for v1.32 (correct me, if otherwise)

Here's where this enhancement currently stands:

• KEP readme using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable for latest-milestone: v1.32.
• KEP readme has up-to-date graduation criteria
• KEP has a production readiness review that has been completed and merged into k/enhancements. (For more information on the PRR process, check here). If your production readiness review is not completed yet, please make sure to fill the production readiness questionnaire in your KEP by the PRR Freeze deadline on Thursday 3rd October 2024 so that the PRR team has enough time to review your KEP.

For this KEP, we would just need to update the following:

• Ensure KEP readme using the latest template
• Update kep.yaml to mention latest-milestone: v1.32 and stable: "v1.32"
• Complete the PRR review process for stable stage and merge it into k/enhancements.
• Update kep.yaml to mention stage: stable

It looks like #4812 will address most of these issues.

• Get KEP-1967: promote size memory backed volumes to stable #4812 merged before the enhancements freeze.

The status of this enhancement is marked as at risk for enhancement freeze. Please keep the issue description up-to-date with appropriate stages as well.

If you anticipate missing enhancements freeze, you can file an exception request in advance. Thank you!

[sohankunkerkar]

@kannon92 could you address this comment and prepare #4812 for the PRR review?

[kannon92]

@kannon92 could you address this comment and prepare #4812 for the PRR review?

I addressed these comments and PRR reviewing is ongoing.

[kannon92]

I also opened up kubernetes/website#48254 to reflect the website changes.

[dipesh-rawat]

Hi @kannon92 👋, v1.32 Enhancements team here.

Just a quick friendly reminder as we approach the enhancements freeze later this week, at 02:00 UTC Friday 11th October 2024 / 19:00 PDT Thursday 10th October 2024.

The current status of this enhancement is marked as at risk for enhancement freeze. There are a few requirements mentioned in the comment #1967 (comment) that still need to be completed.

It looks like PR #4812 will address most of these issues. The PR #4812 needs to be merged before the enhancements freeze.

If you anticipate missing enhancements freeze, you can file an exception request in advance. Thank you!

[dipesh-rawat]

@kannon92 With PR #4812 has been merged, almost all the KEP requirements are in place. We also need a update in the kep.yaml to set the stage: stable. Could you please make this update to the kep.yaml?

[kannon92]

#4916

[dipesh-rawat]

@kannon92 Thanks for the quick fix as part of #4916. With that merged, all the KEP requirements are in place and merged into k/enhancements.

The status of this enhancement is now marked as tracked for enhancement freeze. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

[michellengnx]

Hello @derekwaynecarr, @kannon92 and @mvortizr 👋, 1.32 Docs Shadow here.
Does this enhancement work planned for 1.32 require any new docs or modification to existing docs?
If so, please follows the steps here to open a PR against dev-1.32 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday October 24th 2024 18:00 PDT.
Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.
Thank you!

[kannon92]

Here is an update on feature:

Code PRs: kubernetes/kubernetes#126981
Doc PRs: kubernetes/website#48254

[kannon92]

I cannot edit the description so if someone else wants to add this to the description that would be great. I don't think I need to create a new issue.

[rytswd]

Hi @derekwaynecarr @kannon92 👋 -- this is Ryota (@rytswd) from the v1.32 Communications Team!

For the v1.32 release, we are currently in the process of collecting and curating a list of potential feature blogs, and we'd love for you to consider writing one for your enhancement!

As you may be aware, feature blogs are a great way to communicate to users about features which fall into (but not limited to) the following categories:

• This introduces some breaking change(s)
• This has significant impacts and/or implications to users
• ...Or this is a long-awaited feature, which would go a long way to cover the journey more in detail 🎉

To opt in to write a feature blog, could you please let us know and open a "Feature Blog placeholder PR" (which can be only a skeleton at first) against the website repository by Wednesday, 30th Oct 2024? For more information about writing a blog, please find the blog contribution guidelines 📚

Tip

Some timeline to keep in mind:

• 02:00 UTC Wednesday, 30th Oct: Feature blog PR freeze
• Monday, 25th Nov: Feature blogs ready for review
• You can find more in the release document

Note

In your placeholder PR, use XX characters for the blog date in the front matter and file name. We will work with you on updating the PR with the publication date once we have a final number of feature blogs for this release.

[dipesh-rawat]

Hey again @kannon92 👋 v1.32 Enhancements team here,

Just checking in as we approach code freeze at 02:00 UTC Friday 8th November 2024 / 19:00 PDT Thursday 7th November 2024 .

Here's where this enhancement currently stands:

• All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
• All PR/s are ready to be merged (they have approved and lgtm labels applied) by the code freeze deadline. This includes tests.

For this enhancement, it looks like the following PRs are open and need to be merged before code freeze (and we need to update the Issue description to include all the related PRs of this KEP):

• KEP-1967: promote size backed memory volumes to stable kubernetes#126981

Additionally, please let me know if there are any other PRs in k/k not listed in the description or linked with this GitHub issue that we should track for this KEP, so that we can maintain accurate status.

The status of this enhancement is marked as at risk for code freeze.

If you anticipate missing code freeze, you can file an exception request in advance. Thank you!

[rytswd]

Hi @derekwaynecarr @kannon92 👋, v1.32 Communications Team here again!

This is a gentle reminder for the feature blog deadline mentioned above, which is 02:00 UTC Wednesday, 30th Oct. To opt in, please let us know and open a Feature Blog placeholder PR against k/website by the deadline. If you have any questions, please feel free to reach out to us!

Tip

Some timeline to keep in mind:

• 02:00 UTC Wednesday, 30th Oct: Feature blog PR freeze
• Monday, 25th Nov: Feature blogs ready for review
• You can find more in the release document

Note

In your placeholder PR, use XX characters for the blog date in the front matter and file name. We will work with you on updating the PR with the publication date once we have a final number of feature blogs for this release.

[dipesh-rawat]

Hello @kannon92 👋, v1.32 Enhancements team here

With all the implementation(code related) PRs merged as per the issue description:

• KEP-1967: promote size backed memory volumes to stable kubernetes#126981

This enhancement is now marked as tracked for code freeze for the v1.32 Code Freeze!

Additionally, please do let me know if there are any other PRs in k/k not listed in the description that we should track for this KEP, so that we can maintain accurate status.

[haircommander]

/reopen

A github workflow autoclosed when I set to done 🙃 sorry for the noise

[k8s-ci-robot]

@haircommander: Reopened this issue.

In response to this:

/reopen

A github workflow autoclosed when I set to done 🙃 sorry for the noise

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.