Enhancements: Add support for online resizing of PVs

[mlmhl]

Feature Description

• Allow PVs to be resized without having to terminate pods and unmount volume first.
• Primary contact (assignee): @mlmhl
• Responsible SIGs: @kubernetes/sig-storage-feature-requests
• Design proposal link (community repo): kubernetes/community#1535
• KEP: 20190125-online-growing-persistent-volume-size
• Link to e2e and/or unit tests:
• Reviewer(s) - (for LGTM) recommend having 2+ reviewers: @saad-ali @gnufied
• Approver (likely from SIG/area to which feature belongs): @jsafrane
• Feature target (which target equals to which milestone):
  
  
  
  • Alpha release target (x.y): 1.11
  
  
  • Beta release target (x.y): 1.15
  
  
  • Stable release target (x.y): 1.xx
  
  

[mlmhl]

This is a sub feature of this feature.

[idvoretskyi]

/assign @mlmhl

[idvoretskyi]

/sig storage

[Bradamant3]

@mlmhl doc PR, please? also please update the 1.10 feature tracking spreadsheet
It looks as though there are several related features going into this release; I'm tracking them for docs purposes per the spreadsheet. lmk if something else would work better. Also if one doc PR covers multiple issues, if you tag the issues in the doc PR, that will help. Thanks!

[Bradamant3]

@mlmhl docs ping ^^
/cc @idvoretskyi

[gnufied]

This feature did make make into 1.10 milestone. Please drop this from the list.

[justaugustus]

@mlmhl @gnufied
Any plans for this in 1.11?

If so, can you please ensure the feature is up-to-date with the appropriate:

• Description
• Milestone
• Assignee(s)
• Labels:
  
  
  
  • stage/{alpha,beta,stable}
  
  
  • sig/*
  
  
  • kind/feature
  
  

cc @idvoretskyi

[mlmhl]

@justaugustus Yeah, we are working on this feature now, the doc PR and code PR are both posted.
The Milestone and Labels are already updated, are these correct?

[justaugustus]

@mlmhl looks good. Just wanted to confirm before committing this to the 1.11 Features list. Thanks again!

[mdlinville]

@mlmhl please fill out the appropriate line item of the
1.11 feature tracking spreadsheet
and open a placeholder docs PR against the
release-1.11 branch
by 5/25/2018 (tomorrow as I write this) if new docs or docs changes are
needed and a relevant PR has not yet been opened.

[mlmhl]

@mistyhacks done.

[mdlinville]

Thanks for marking that it needs docs. I was not able to find the placeholder PR in order to put it in the 1.11 milestone. Can you point me to it?

[justaugustus]

@mlmhl -- this feature has been moved to the Milestone risks sheet within the 1.11 Features tracking spreadsheet.

Please update the line item for this feature on the Milestone risks sheet ASAP AND ping myself and @idvoretskyi, so we can assess the feature status or we will need to officially remove it from the milestone.

[gnufied]

@mlmhl the docs PR has to be opened https://github.com/kubernetes/website .

[gnufied]

@mlmhl @justaugustus I have opened https://github.com/kubernetes/website/pull/8896 which includes documentation for this feature as well. PTAL.

I have also updated the feature spreadhsheet with new information.

[justaugustus]

Thanks @gnufied! I'm moving it back to the main sheet.

[kacole2]

@mlmhl @gnufied This feature was worked on in the previous milestone, so we'd like to check in and see if there are any plans for this to graduate stages in Kubernetes 1.12 as mentioned in your original post. This still has the 1.11 milestone as well so we need to update it accordingly.

If there are any updates, please explicitly ping @justaugustus, @kacole2, @robertsandoval, @rajendar38 to note that it is ready to be included in the Features Tracking Spreadsheet for Kubernetes 1.12.

---

Please note that the Features Freeze is July 31st, after which any incomplete Feature issues will require an Exception request to be accepted into the milestone.

In addition, please be aware of the following relevant deadlines:

• Docs deadline (open placeholder PRs): 8/21
• Test case freeze: 8/28

Please make sure all PRs for features have relevant release notes included as well.

Happy shipping!

[gnufied]

This feature will target beta in 1.12.

[justaugustus]

Thanks for the update! This has been added to the 1.12 Tracking sheet.

/remove-stage alpha
/stage beta

[zparnold]

Hey there! @mlmhl I'm the wrangler for the Docs this release. Is there any chance I could have you open up a docs PR against the release-1.12 branch as a placeholder? That gives us more confidence in the feature shipping in this release and gives me something to work with when we start doing reviews/edits. Thanks! If this feature does not require docs, could you please update the features tracking spreadsheet to reflect it?

[mlmhl]

Hey @zparnold , thanks for reminding! @gnufied has already submitted the doc PR of this feature in 1.11, and we intend to move it to beta in 1.12. So what I need to do is opening up a doc PR against the release-1.12 branch to update the feature state?

[zparnold]

That would be correct! Thanks!

[wongma7]

@zparnold @mlmhl I've created a placeholder/WIP docs PR here https://github.com/kubernetes/website/pull/10101

[mlmhl]

Thanks @wongma7 !

[zparnold]

Thanks!

On Wed, Aug 29, 2018 at 4:30 AM mlmhl [e-mail] wrote:

Thanks @wongma7 https://github.com/wongma7 !

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/features/issues/531#issuecomment-416919812,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AE81SOLb8oRiq2amrfEpM7U2VK86wzp9ks5uVntVgaJpZM4RIUIq
.

[justaugustus]

@mlmhl @wongma7 --
Any update on docs status for this feature? Are we still planning to land it for 1.12?
At this point, code freeze is upon us, and docs are due on 9/7 (2 days).
If we don't here anything back regarding this feature ASAP, we'll need to remove it from the milestone.

cc: @zparnold @jimangel @tfogo

[justaugustus]

@mlmhl @wongma7 --
We haven't heard back from you and at this point, docs are overdue.

I'm removing this from the milestone. If you feel this is incorrect, please let me know ASAP.

/milestone clear

[gnufied]

yeah that seems fair. The changes needed for this PR didn't get merged.

[kacole2]

Hi @mlmhl @gnufied
This enhancement has been tracked before, so we'd like to check in and see if there are any plans for this to graduate stages in Kubernetes 1.13. This release is targeted to be more ‘stable’ and will have an aggressive timeline. Please only include this enhancement if there is a high level of confidence it will meet the following deadlines:
Docs (open placeholder PRs): 11/8
Code Slush: 11/9
Code Freeze Begins: 11/15
Docs Complete and Reviewed: 11/27

Please take a moment to update the milestones on your original post for future tracking and ping @kacole2 if it needs to be included in the 1.13 Enhancements Tracking Sheet

Thanks!

[mlmhl]

@kacole2 Yeah, we intend to move this enhancement to beta in 1.13, but I'm not sure what I need to do, could you help to point it out?

[kacole2]

@mlmhl i'll take care of the labels. you take care of the code and docs. sound like a plan? ;)
/milestone v1.13

[mlmhl]

Thanks @kacole2 ! The doc and code PR are as shown below, is this the right way?

doc: kubernetes/website#10574
code: kubernetes/kubernetes#67608

[kacole2]

@mlmhl thats perfect. that will make wrangling much easier going forward.

[guineveresaenger]

@wongma7 @mlmhl @gnufied I'm Enhancements Shadow for 1.13. Could you please update the release team with the likelihood of this enhancement making the 1.13 release?

Code slush begins on 11/9 and code freeze is 11/15.

Thank you!

[wongma7]

@guineveresaenger update, after the sig-storage meeting yesterday, decision was made to delay this alpha->beta promotion another release because there is some concern a bug similar to one that was discovered recently could affect this feature (cc @gnufied @mlmhl )

[claurence]

@mlmhl Hello - I’m the enhancement’s lead for 1.14 and I’m checking in on this issue to see what work (if any) is being planned for the 1.14 release. Enhancements freeze is Jan 29th and I want to remind that all enhancements must have a KEP

[mlmhl]

@claurence Yeah, we plan to improve this feature to beta in 1.14, the doc PR is here: https://github.com/kubernetes/website/pull/10574.

[claurence]

@mlmhl thanks! Does this issues have a KEP? We want all issues in the 1.14 release to have a KEP associated with them. Thanks

[mlmhl]

Yeah, we have a proposal PR here: https://github.com/kubernetes/community/pull/1535, but I am not sure if it is in order.

[claurence]

@mlmhl since theKEP for this issue isn't merged yet we will be removing it from the 1.14 milestone. To have it added back in please file an exception - information on the exception process can be found here: https://github.com/kubernetes/sig-release/blob/master/releases/EXCEPTIONS.md

[wongma7]

@claurence there was a PR open here. https://github.com/kubernetes/enhancements/pull/737. does a kep need to be merged or just open. I cannot find where it says that a KEP needs to be merged, only that an issue must exist (this one): https://github.com/kubernetes/sig-release/tree/master/releases/release-1.14#enhancements-freeze

[claurence]

@wongma7 KEP needs to be merged and implementable - apologies we need to update our documentation to reflect that

[kacole2]

Hello @wongma7 @mlmhl , I'm the Enhancement Lead for 1.15. Is this feature going to be graduating alpha/beta/stable stages in 1.15? Please let me know so it can be tracked properly and added to the spreadsheet. KEP needs to be merged to be promoted

Once coding begins, please list all relevant k/k PRs in this issue so they can be tracked properly.

[gnufied]

This feature is going beta in 1.15

[kacole2]

/milestone v1.15

[kacole2]

@gnufied @wongma7 @mlmhl, Kubernetes 1.15 Enhancement Freeze is 4/30/2019. To be included in the Kubernetes 1.15 milestone, KEPs are required to be merged and in an "Implementable" state with proper test plans and graduation criteria. I do not see any KEPs listed here. Community Proposals are deprecated and a KEP needs to be created. If this will slip from the 1.15 milestone, please let us know so we can make appropriate tracking changes.

[kacole2]

@gnufied @wongma7 @mlmhl I apologize, I see this 20190125-online-growing-persistent-volume-size. I will add this to the original post so it's not buried.

[simplytunde]

Hey @mlmhl Just a friendly reminder we're looking for a PR against k/website (branch dev-1.15) due by Thursday, May 30. It would be great if it's the start of the full documentation, but even a placeholder PR is acceptable. Let me know if you have any questions!

[simplytunde]

@gnufied @mlmhl @wongma7 The placeholder PR is due Thursday May 30th.

[kacole2]

Hi @gnufied @mlmhl @wongma7 . Code Freeze is Thursday, May 30th 2019 @ EOD PST. All enhancements going into the release must be code-complete, including tests, and have docs PRs open.

Please list all current k/k PRs so they can be tracked going into freeze. If the PRs aren't merged by freeze, this feature will slip for the 1.15 release cycle. Only release-blocking issues and PRs will be allowed in the milestone.

If you know this will slip, please reply back and let us know. Thanks!

[kacole2]

Hi @gnufied @mlmhl @wongma7, today is code freeze for the 1.15 release cycle. I do not see a reply for any k/k PRs to track for this merge. It's now being marked as At Risk in the 1.15 Enhancement Tracking Sheet. If there is no response, or you respond with PRs to track and they are not merged by EOD PST, this will be dropped from the 1.15 Milestone. After this point, only release-blocking issues and PRs will be allowed in the milestone with an exception.

[gnufied]

The correct link for code PR is https://github.com/kubernetes/kubernetes/pull/77755 . I will open docs PR soonish.

[gnufied]

Placeholder docs PR - https://github.com/kubernetes/website/pull/14643

[kacole2]

Hi @mlmhl @gnufied , I'm the 1.16 Enhancement Lead. Is this feature going to be graduating alpha/beta/stable stages in 1.16? Please let me know so it can be added to the 1.16 Tracking Spreadsheet. If not's graduating, I will remove it from the milestone and change the tracked label.

Once coding begins or if it already has, please list all relevant k/k PRs in this issue so they can be tracked properly.

Milestone dates are Enhancement Freeze 7/30 and Code Freeze 8/29.

Thank you.

[annajung]

Hello @mlmhl , 1.17 Enhancement Shadow here! 🙂

I wanted to reach out to see *if this enhancement will be graduating to alpha/beta/stable in 1.17?

*
Please let me know so that this enhancement can be added to 1.17 tracking sheet.

Thank you!

🔔Friendly Reminder

• The current release schedule is
  
  
  
  • Monday, September 23 - Release Cycle Begins
  
  
  • Tuesday, October 15, EOD PST - Enhancements Freeze
  
  
  • Thursday, November 14, EOD PST - Code Freeze
  
  
  • Tuesday, November 19 - Docs must be completed and reviewed
  
  
  • Monday, December 9 - Kubernetes 1.17.0 Released
  
  

• A Kubernetes Enhancement Proposal (KEP) must meet the following criteria before Enhancement Freeze to be accepted into the release

  • PR is merged in
  • In an implementable state
  • Include test plan and graduation criteria

• All relevant k/k PRs should be listed in this issue

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[palnabarun]

/remove-lifecycle stale

[gnufied]

For 1.18 this feature will remain in beta but we are planning enhancements that will move it closer to GA release.

[palnabarun]

Thank you @gnufied for the updates.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[palnabarun]

/remove-lifecycle stale

[palnabarun]

Hi @gnufied -- 1.19 Enhancements Lead here, I wanted to check in if you think this enhancement would graduate in 1.19?

---

The current release schedule is:

• Monday, April 13: Week 1 - Release cycle begins
• Tuesday, May 19: Week 6 - Enhancements Freeze
• Thursday, June 25: Week 11 - Code Freeze
• Thursday, July 9: Week 14 - Docs must be completed and reviewed
• Tuesday, August 4: Week 17 - Kubernetes v1.19.0 released
• Thursday, August 20: Week 19 - Release Retrospective

[gnufied]

@palnabarun thank you for the ping. We are proposing further API changes in 1.19 release which will enable this feature along with general resizing(https://github.com/kubernetes/enhancements/issues/284) to go GA.

We are trying to get https://github.com/kubernetes/enhancements/pull/1516 merged to that end.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[palnabarun]

/remove-lifecycle stale

[kikisdeliveryservice]

Hi @gnufied @mlmhl

Enhancements Lead here. Any plans to graduate this in 1.20?

Thanks,
Kirsten

[kikisdeliveryservice]

Hi @gnufied @mlmhl

Any updates on this for 1.20?

Thanks,
Kirsten