-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Support Volume Expansion Through StatefulSets #661
Comments
/kind feature |
@kubernetes/sig-apps-feature-requests |
@SidakM - Hello I'm the enhancements lead for 1.14. It looks like this issue is targeting 1.14 for alpha can you let me know if that is still planned. Enhancements freeze is Jan 29th and we want all issues to have a KEP associated with them. |
Hey @claurence , |
@SidakM: Reiterating the mentions to trigger a notification: In response to this:
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. |
@SidakM checking in as enhancements freeze is on Tuesday - was the KEP reviewed? Are there any open PRs to track for the 1.14 cycle? |
@claurence Someone looked and commented but didn't follow up after so I am unsure where its at. |
@SidakM 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 |
@claurence it is critical functionality for stateful applications like databases. |
@delgod because we have passed enhancement freeze and the KEP still is not merged please submit an exception request. |
Can we see something similar for DaemonSets? |
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. Enhancements do require a KEP as well. Once coding begins, please list all relevant k/k PRs in this issue so they can be tracked properly. |
/assign @SidakM |
@gnufied Can we get this in for 1.15? |
Hi @SidakM , I'm the 1.16 Enhancement 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. 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 merged into the k/e repo. The KEp is currently still open Milestone dates are Enhancement Freeze 7/30 and Code Freeze 8/29. Thank you. |
Why is this feature request keeps getting pushed to one Enhancement to another...? This is very important, not only for databases but also for Kafka clusters in production! Although it's possible to replicate to a new cluster with more storage, and then swtich over, it's not a viable solution. We need this! |
@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 |
Currently we are using StatefulSet volumeClaimTemplate to provision the PVC. However the corresponding StatefulSet field that controls the PVC size is immutable. It is not possible to resize/enlarge the underlying PVC through the StatefulSet spec. See kubernetes/enhancements#661 This commit makes the cache size field immutable until we decide how to implement the resize.
Currently we are using StatefulSet volumeClaimTemplate to provision the PVC. However the corresponding StatefulSet field that controls the PVC size is immutable. It is not possible to resize/enlarge the underlying PVC through the StatefulSet spec. See kubernetes/enhancements#661 This commit makes the cache size field immutable until we decide how to implement the resize.
Currently we are using StatefulSet volumeClaimTemplate to provision the PVC. However the corresponding StatefulSet field that controls the PVC size is immutable. It is not possible to resize/enlarge the underlying PVC through the StatefulSet spec. See kubernetes/enhancements#661 This commit makes the cache size field immutable until we decide how to implement the resize.
Currently we are using StatefulSet volumeClaimTemplate to provision the PVC. However the corresponding StatefulSet field that controls the PVC size is immutable. It is not possible to resize/enlarge the underlying PVC through the StatefulSet spec. See kubernetes/enhancements#661 This commit makes the cache size field immutable until we decide how to implement the resize.
* Make the cache size field immutable Currently we are using StatefulSet volumeClaimTemplate to provision the PVC. However the corresponding StatefulSet field that controls the PVC size is immutable. It is not possible to resize/enlarge the underlying PVC through the StatefulSet spec. See kubernetes/enhancements#661 This commit makes the cache size field immutable until we decide how to implement the resize. * Address review comments
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 |
/remove-lifecycle stale |
/lifecycle frozen |
@harshanarayana any news on this? |
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 |
It's going to be really helpful |
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. |
Enhancement Description
Please to keep this description up to date. This will help the Enhancement Team track efficiently the evolution of the enhancement
The text was updated successfully, but these errors were encountered: