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
• 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.12
  • Stable release target (x.y): 1.13?

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

[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: kubernetes/website#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: kubernetes/community#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. #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