search

kubernetes / enhancements

Enhancements tracking repo for Kubernetes
Apache License 2.0
3.46k stars 1.49k forks source link

Support Volume Expansion Through StatefulSets #661

Open SidakM-zz opened 5 years ago

SidakM-zz commented 5 years ago

Enhancement Description

Please to keep this description up to date. This will help the Enhancement Team track efficiently the evolution of the enhancement

Priyankasaggu11929 commented 2 years ago

Hello @shalini-b @SidakM-zz @janetkuo 👋

I'm checking in once again, as we approach the 1.24 enhancements freeze next week, on Thursday, February 3rd, 2022 at 18:00 PM PT.

Currently the status of the enhancement is at risk.

Looks like, for this enhancement to be tracked into the 1.24 release, it would require updating the following open KEP PR to add a PRR review file, and getting it merged before the enhancements freeze.

Also please update the issue description with appropriate stages & links (it helps with release team's tracking progress). Thank you so much once again! 🙂

gracenng commented 2 years ago

The Enhancements Freeze is now in effect and this enhancement is removed from the release. Please feel free to file an exception.

/milestone clear

KlavsKlavsen commented 2 years ago

pushed once again ? no one has the time to code it? or no one thinks its important enough? :( It REALLY beats having to do a delete with no cascade (to keep pods and pvcs) and then re-creating the statefulset - hoping it reconnects with existing pods and pvcs :).

R-Studio commented 2 years ago

Any news?

k8s-triage-robot commented 2 years ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

invidian commented 2 years ago

/remove-lifecycle stale

k8s-triage-robot commented 2 years ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

sastorsl commented 2 years ago

/remove-lifecycle stale

R-Studio commented 1 year ago

Any news? (this is a 4 years old issue 😐😖)

dims commented 1 year ago

@R-Studio time for someone interested in this to step up and do the work.

https://twitter.com/dims/status/1593348306054397952?s=20&t=PuhfxZlKxw1B-V-QJFsbIg

R-Studio commented 1 year ago

@dims I would really like to but unfortunately i am not a developer or have enough experience with kubernetes in general (I have only been working with kubernetes for 6 months). Maybe I can help in years 😅

davidkarlsen commented 1 year ago

@R-Studio time for someone interested in this to step up and do the work.

https://twitter.com/dims/status/1593348306054397952?s=20&t=PuhfxZlKxw1B-V-QJFsbIg

Actually a KEP already exists: https://github.com/kubernetes/enhancements/pull/2842

harshanarayana commented 1 year ago

@dims I would really love to help take this one further it that is all right. How do I go about it ? Do I open a new PR inheriting what is in https://github.com/kubernetes/enhancements/pull/2842 and addressing the comments from it ?

dims commented 1 year ago

@harshanarayana i'd recommend talking to the sig-storage leadership - https://github.com/kubernetes/community/tree/master/sig-storage#leadership

try async first (email sig-storage mailing list and slack) as you are in IST. you may have to get on their agenda/calendar (sig storage meeting) if that does not work.

xing-yang commented 1 year ago

This enhancement issue has actually been in our tracking spreadsheet which we go over in every SIG Storage meeting. It has not got an update for while but design discussions just started again on the KEP: https://github.com/kubernetes/enhancements/pull/3412

harshanarayana commented 1 year ago

@xing-yang This is now being actively discussed with the help of @gnufied and @jsafrane . @areller and I are working together on the KEP. Thanks

k8s-triage-robot commented 10 months ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

blafry commented 10 months ago

/remove-lifecycle stale

ialidzhikov commented 10 months ago

/lifecycle frozen

R-Studio commented 10 months ago

@harshanarayana any news on this?

KlavsKlavsen commented 10 months ago

Yeah - this would really be nice to support - it makes production harder than it needs to be - having to delete and recreate statefulsets - ensuring pods aren't killed with cascade=false

usharik commented 9 months ago

It's going to be really helpful

harshanarayana commented 9 months ago

I got side tracked with a few other work and same seem to be the case with @areller . But let me get back to that old Document and put up an updated one for discussion again.

huww98 commented 6 months ago

We have created #4650 , and working on it at #4651 . The new KEP allows arbitrary changes to the volumeClaimTemplates, it should cover the use-case of this KEP, and more.

soltysh commented 5 months ago

@huww98 does this means you're replacing #661 and we should close the other?