Re: [kubernetes/enhancements] Add resizing support to CSI volumes (#556)
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
—
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.
Michelle Au
/remove-lifecycle stale
Claire Laurence
@gnufied 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
Hemant Kumar
@claurence this feature is on track for 1.14 yes!
Claire Laurence
Thanks @gnufied based on the label is it still alpha or is it graduating in 1.14. Also are there any associated open PRs for this issue or have they all been merged?
Claire Laurence
@gnufied checking in on this feature? Is this planning to graduate or is it planning to be alpha in 1.14? The label on it indicates alpha. Additionally is there a KEP for this issue?
Hemant Kumar
This feature will release as an alpha feature in 1.14. As such we weren't planning for a KEP because it does not require a major redesign in existing internals it builds on feature that already exists in k8s.
Claire Laurence
@gnufied I think we'd still want a KEP - is there a testing plan for this enhancement? graduation criteria?
Hemant Kumar
@claurence added a KEP for csi volume resizing.
Claire Laurence
@gnufied Thanks - since the KEP 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
Claire Laurence
Adding back to 1.14 milestone. Thanks for getting the KEP merged
Cody Clark
Hi @gnufied! I'm one of the v1.14 docs release shadows.
Does this enhancement require any new docs (or modifications)?
Just a friendly reminder we're looking for a PR against k/website (branch dev-1.14) due by Friday, March 1. 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!
Lachlan Evenson
Hello @gnufied, 1.14 enhancement shadow here. Code Freeze is March 7th and all PRs must be merged by then to your issue to make the 1.14 release. What open K/K PRs do you still have that need to merge? Thanks
Hemant Kumar
@lachie83 @cody-clark The feature is on track. Most of work is externally done in https://github.com/kubernetes-csi/external-resizer/ , however I will have a PR for main k/k repo as well.
I will open docs PR by docs window.
Hemant Kumar
Docs PR - kubernetes/website#12928
Hemant Kumar
Code PR for main k/k repo - kubernetes/kubernetes#74863
Jim Angel
Hey @gnufied, thanks for the docs ref. Would you mind rebasing it off of the dev-1.14 branch instead of master? Thanks!
Kendrick Coleman
@gnufied did this go to stable in 1.14? If so, let's close out this issue. If not, any work planned for 1.15?
/milestone clear
Michelle Au
This is alpha in 1.14, and is planned to move to beta in 1.15
Kendrick Coleman
/milestone v1.15
/stage beta
simplytunde
Hey @gnufied . We need a placeholder PR checked in against dev-1.15 branch. This is due by Thursday, May 30. Thanks!
simplytunde
@gnufied The placeholder PR is due Thursday May 30th.
Kendrick Coleman
Hi @gnufied @msau42 . 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.
For this issues I'm seeing kubernetes/kubernetes#74863 is merged, kubernetes-sigs/azurefile-csi-driver#43 is open and kubernetes/kubernetes#67608 is open. If there are some missing please let me know what needs to be merged by Thursday.
If you know this will slip, please reply back and let us know. Thanks!
Kendrick Coleman
Hi @gnufied @msau42, today is code freeze for the 1.15 release cycle. The k/k PR kubernetes/kubernetes#67608 has not yet been merged. It's now being marked as At Risk in the 1.15 Enhancement Tracking Sheet. Is there a high confidence this will be merged by EOD PST today? After this point, only release-blocking issues and PRs will be allowed in the milestone with an exception.
Hemant Kumar
This feature is not moving to beta in 1.15. It remains in alpha. We are making some additional changes but features themselves won't change.
Hemant Kumar
@kacole2 also kubernetes/kubernetes#77755 is replacement PR for kubernetes/kubernetes#67608
Kendrick Coleman
/milestone clear
/stage alpha
Hemant Kumar
We are targeting this feature to beta in 1.16.
Kendrick Coleman
/milestone v1.16
/stage beta
simplytunde
Hey, @gnufied I'm the v1.16 docs release lead.
Does this enhancement (or the work planned for v1.16) require any new docs (or modifications)?
Just a friendly reminder we're looking for a PR against k/website (branch dev-1.16) due by Friday,August 23rd. 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!
Hemant Kumar
I will have docs PR by eod today. thank you.
simplytunde
@gnufied Please at me once the Doc is out and I will be tracking also.
Hemant Kumar
placeholder PR is here - kubernetes/website#16043
simplytunde
Thanks @gnufied
Kendrick Coleman
@gnufied friendly reminder that code freeze for 1.16 is on Thursday 8/29. Are there any outstanding k/k PRs besides kubernetes/kubernetes#81877 that still need to be merged for this to go Beta?
Hemant Kumar
yes that is the main PR. Although we are also tracking kubernetes/kubernetes#81467 for 1.16 so as we could run the e2e tests against more CSI drivers
Hemant Kumar
Correction - we are trying to get kubernetes/kubernetes#81467 as the main PR because it will improve e2e coverage, in addition to enabling the CSI volume expansion feature gate.
Bob Killen
Hey there @gnufied -- 1.17 Enhancements lead here. I wanted to check in and see if you think this Enhancement will be graduating to alpha/beta/stable in 1.17?
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
If you do, please list all relevant k/k PRs in this issue so they can be tracked properly. 👍
/milestone clear
Hemant Kumar
We will most likely keep this feature in beta in 1.17 and focus on making it more stable.
Bob Killen
Great! Thanks for the quick response! 👍
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
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
Anton Bessonov
/remove-lifecycle stale
Nabarun Pal
Hey there @gnufied -- 1.18 Enhancements shadow here. I wanted to check in and see if you think this Enhancement will be graduating to stable in 1.18 or having a major change in its current level?
The current release schedule is:
- Monday, January 6th - Release Cycle Begins
- Tuesday, January 28th EOD PST - Enhancements Freeze
- Thursday, March 5th, EOD PST - Code Freeze
- Monday, March 16th - Docs must be completed and reviewed
- Tuesday, March 24th - Kubernetes 1.18.0 Released
If you would like to include this enhancement, once coding begins please list all relevant k/k PRs in this issue so they can be tracked properly. 👍
We'll be tracking enhancements here: http://bit.ly/k8s-1-18-enhancementsThanks!
Thanks! :)
Nabarun Pal
@gnufied Just a friendly reminder, we are just 7 days away from the Enhancement Freeze (Tuesday, January 28th).
Nabarun Pal
@gnufied Just a friendly reminder, we are just 2 days away from the Enhancement Freeze (3 PM Pacific Time, Tuesday, January 28th).
Nabarun Pal
Unfortunately, the deadline for the 1.18 Enhancement freeze has passed. For now, this is being removed from the milestone. If there is a need to get this in, please file an enhancement exception.
Bruno
@palnabarun any chance of this making to the next release? This is an inevitable step in many workflows.
Michelle Au
@bratao this is available in beta since 1.16. Are you asking about GA? The current plan for 1.19 is to keep the feature in beta and continue fixing bugs and corner cases.
Bruno
@msau42 oh I somehow missed it. Thanks!!!
Mirek Sedzinski
Hey there @gnufied -- 1.19 Enhancements shadow here. I wanted to check in and see if you think this Enhancement will be graduating in 1.19?
In order to have this part of the release:
- The KEP PR must be merged in an implementable state
- The KEP must have test plans
- The KEP must have graduation criteria.
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
If you do, I'll add it to the 1.19 tracking sheet (http://bit.ly/k8s-1-19-enhancements). Once coding begins please list all relevant k/k PRs in this issue so they can be tracked properly. 👍
Thanks!
Mirek Sedzinski
Mirek Sedzinski
Hemant Kumar
We are not graduating this feature to GA. Having said that, we are working to transition this feature to GA while fixing open issues and addressing pending concerns.
Mirek Sedzinski
Thank you @gnufied for letting me know.
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
—
Hemant Kumar
/remove-lifecycle stale
Kirsten
Hemant Kumar
This will remain in beta in 1.20 we are working on issues such as recovery from resize failure etc before this can be moved to GA,
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
—
Anton Bessonov
/remove-lifecycle stale
Anton Bessonov
Please, remove the stale bot. I hate the messages from stale bot. I hate to notify all subscribers with /remove-lifecycle stale messages. Stale bot is a good way to show your disrespect to the community.
Mateusz Gozdek
Or at least someone do life cycle freeze here..
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-contributor-experience at kubernetes/community.
/lifecycle stale
Anton Bessonov
/remove-lifecycle stale
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-contributor-experience at kubernetes/community.
/lifecycle stale
Anton Bessonov
/remove-lifecycle stale
Anton Bessonov
/lifecycle frozen