Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add resizing support to CSI volumes #556

Open
gnufied opened this issue Apr 12, 2018 · 79 comments
Open

Add resizing support to CSI volumes #556

gnufied opened this issue Apr 12, 2018 · 79 comments
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. sig/storage Categorizes an issue or PR as relevant to SIG Storage. stage/beta Denotes an issue tracking an enhancement targeted for Beta status tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team

Comments

@gnufied
Copy link
Member

gnufied commented Apr 12, 2018

Enhancement Description

@gnufied
Copy link
Member Author

gnufied commented Apr 12, 2018

/assign

@gnufied
Copy link
Member Author

gnufied commented Apr 12, 2018

/sig storage

@k8s-ci-robot k8s-ci-robot added the sig/storage Categorizes an issue or PR as relevant to SIG Storage. label Apr 12, 2018
@idvoretskyi idvoretskyi added this to the v1.11 milestone Apr 12, 2018
@idvoretskyi idvoretskyi added the stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status label Apr 12, 2018
@justaugustus
Copy link
Member

justaugustus commented Apr 29, 2018

/kind feature

@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Apr 29, 2018
@justaugustus justaugustus added the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label Apr 29, 2018
@gnufied
Copy link
Member Author

gnufied commented May 30, 2018

We should move this to 1.12. We still have CSI spec change under discussion.

@justaugustus justaugustus modified the milestones: v1.11, v1.12 May 31, 2018
@justaugustus justaugustus removed the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label May 31, 2018
@justaugustus
Copy link
Member

justaugustus commented Jul 18, 2018

@gnufied @kubernetes/sig-storage-feature-requests --

This feature was removed from the previous milestone, so we'd like to check in and see if there are any plans for this in Kubernetes 1.12.

If so, please ensure that this issue is up-to-date with ALL of the following information:

  • One-line feature description (can be used as a release note):
  • Primary contact (assignee):
  • Responsible SIGs:
  • Design proposal link (community repo):
  • Link to e2e and/or unit tests:
  • Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred:
  • Approver (likely from SIG/area to which feature belongs):
  • Feature target (which target equals to which milestone):
    • Alpha release target (x.y)
    • Beta release target (x.y)
    • Stable release target (x.y)

Set the following:

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

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!

/cc @justaugustus @kacole2 @robertsandoval @rajendar38

@gnufied
Copy link
Member Author

gnufied commented Jul 26, 2018

This is still on target for 1.12. We are working on various aspects of code and specs to meet that goal.

@justaugustus
Copy link
Member

justaugustus commented Jul 26, 2018

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

@justaugustus justaugustus added the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label Jul 26, 2018
@zparnold
Copy link
Member

zparnold commented Aug 20, 2018

Hey there! @gnufied 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?

justaugustus pushed a commit to justaugustus/enhancements that referenced this issue Sep 3, 2018
Fix broken link in architecture.md
@justaugustus
Copy link
Member

justaugustus commented Sep 5, 2018

@gnufied --
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 overdue.
If we don't here anything back regarding this feature ASAP, we'll need to remove it from the milestone.

cc: @zparnold @jimangel @tfogo

@gnufied
Copy link
Member Author

gnufied commented Sep 5, 2018

We will have to move this to next milestone.

@justaugustus
Copy link
Member

justaugustus commented Sep 5, 2018

Got it. Thanks for the update!

@justaugustus justaugustus added tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team and removed tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team labels Sep 5, 2018
@justaugustus justaugustus removed this from the v1.12 milestone Sep 5, 2018
@kacole2
Copy link
Member

kacole2 commented Oct 8, 2018

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

We are also now encouraging that every new enhancement aligns with a KEP. If a KEP has been created, please link to it in the original post. Please take the opportunity to develop a KEP.

Thanks!

@fejta-bot
Copy link

fejta-bot commented Jan 6, 2019

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 6, 2019
@msau42
Copy link
Member

msau42 commented Jan 8, 2019

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 8, 2019
@bratao
Copy link

bratao commented Apr 11, 2020

@palnabarun any chance of this making to the next release? This is an inevitable step in many workflows.

@msau42
Copy link
Member

msau42 commented Apr 13, 2020

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

@bratao
Copy link

bratao commented Apr 14, 2020

@msau42 oh I somehow missed it. Thanks!!!

@msedzins
Copy link

msedzins commented Apr 29, 2020

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:

  1. The KEP PR must be merged in an implementable state
  2. The KEP must have test plans
  3. 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!

@msedzins
Copy link

msedzins commented May 1, 2020

Hi @gnufied , kind reminder about my question above.

Thx!

1 similar comment
@msedzins
Copy link

msedzins commented May 4, 2020

Hi @gnufied , kind reminder about my question above.

Thx!

@gnufied
Copy link
Member Author

gnufied commented May 4, 2020

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.

@msedzins
Copy link

msedzins commented May 5, 2020

Thank you @gnufied for letting me know.

@fejta-bot
Copy link

fejta-bot commented Aug 3, 2020

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 3, 2020
@gnufied
Copy link
Member Author

gnufied commented Aug 3, 2020

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 3, 2020
@kikisdeliveryservice
Copy link
Member

kikisdeliveryservice commented Sep 12, 2020

Hi @gnufied

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

Thanks,
Kirsten

@gnufied
Copy link
Member Author

gnufied commented Sep 24, 2020

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
Copy link

fejta-bot commented Dec 23, 2020

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 23, 2020
@Bessonov
Copy link

Bessonov commented Dec 23, 2020

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 23, 2020
@Bessonov
Copy link

Bessonov commented Dec 23, 2020

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.

@invidian
Copy link
Member

invidian commented Dec 23, 2020

Or at least someone do life cycle freeze here..

@fejta-bot
Copy link

fejta-bot commented Mar 23, 2021

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 23, 2021
@Bessonov
Copy link

Bessonov commented Mar 23, 2021

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 23, 2021
@fejta-bot
Copy link

fejta-bot commented Jun 21, 2021

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 21, 2021
@Bessonov
Copy link

Bessonov commented Jun 21, 2021

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 21, 2021
@Bessonov
Copy link

Bessonov commented Jun 21, 2021

/lifecycle frozen

@k8s-ci-robot k8s-ci-robot added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Jun 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. sig/storage Categorizes an issue or PR as relevant to SIG Storage. stage/beta Denotes an issue tracking an enhancement targeted for Beta status tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team
Projects
None yet
Development

No branches or pull requests