Re: [kubernetes/enhancements] Add resize support for FlexVolume (#304)
Claire Laurence
Hi @aniket-s-kulkarni - I'm an enhancements shadow checking in on how this issue is tracking. Code slush is on 11/9 and code freeze is coming up on 11/15 do you have a status update on the likelihood that this will make the the code freeze date?
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
Aniket Kulkarni
@claurence the PR was merged in last week. There is a documentation PR open that I will comment on today so that would be on its way as well.
Aish Sundar
@aniket-s-kulkarni I assume this enhancement is done (except pending docs?)
Aniket Kulkarni
@AishSundar yes that's correct. I think we can close this.
Aniket Kulkarni
/close
k8s-ci-robot
@aniket-s-kulkarni: You can't close an active issue/PR unless you authored it or you are a collaborator.
In response to this:
/close
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/test-infra repository.
Aniket Kulkarni
@AishSundar OK I see.
Aish Sundar
/reopen
@aniket-s-kulkarni thanks for conforming all work pertaining to Alpha in 1.13 is done. But we would like to keep this enhancement issue open for tracking through Beta and GA in future milestones.
Claire Laurence
@xingzhou 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 - I can not find a KEP for this issue, can you please drop a link for the KEP. Thanks
Claire Laurence
@xingzhou since there is no KEP for this issue 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
Aniket Kulkarni
@claurence, I added this support as a part of 1.13 in the last cycle. The feature is still in beta and in this cycle I don't think we are planning any changes.
Kendrick Coleman
Hello @aniket-s-kulkarni @xingzhou , 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. This will also require a KEP to be included.
Once coding begins, please list all relevant k/k PRs in this issue so they can be tracked properly.
Kendrick Coleman
Hi @aniket-s-kulkarni @xingzhou , I'm the 1.16 Enhancement Lead/Shadow. 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.
As a reminder, every enhancement requires a KEP in an implementable state with Graduation Criteria explaining each alpha/beta/stable stages requirements.
Milestone dates are Enhancement Freeze 7/30 and Code Freeze 8/29.
Thank you.
Kubernetes Prow Robot
Closed #304.
Kubernetes Prow Robot
@gnufied: Closing this issue.
In response to this:
I am going to close this feature because feature was implemented and it does not have a feature gate of its own. It will go GA along with general volume expansion feature which is tracked here - #284
/close
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/test-infra repository.
—
Hemant Kumar
I am going to close this feature because feature was implemented and it does not have a feature gate of its own. It will go GA along with general volume expansion feature which is tracked here - #284
/close
—