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!

[mistyhacks]

@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.

[mistyhacks]

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.

[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. #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 kubernetes/kubernetes#77755 . I will open docs PR soonish.

[gnufied]

Placeholder docs PR - kubernetes/website#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.