Support Volume Expansion Through StatefulSets

[SidakM-zz]

Enhancement Description

• One-line enhancement description (can be used as a release note): Allow changes to storage requests in StatefulSets.volumeClaimTemplates to propagate to associated PVCs.
• Primary contact (assignee): @SidakM
• Responsible SIGs: sig-apps
• Design proposal link (community repo): Add StatefulSet Volume Expansion Kep #660, KEP-0661: StatefulSet volume resize #2842
• 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: @janetkuo @gnufied
• Approver (likely from SIG/area to which enhancement belongs):
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y)
  • Beta release target (x.y)
  • Stable release target (x.y)

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

[SidakM-zz]

/kind feature
/sig apps

[janetkuo]

@kubernetes/sig-apps-feature-requests

[claurence]

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

[SidakM-zz]

Hey @claurence ,
Was waiting for a review from @kubernetes/sig-apps-feature-requests . Not sure when one of them will look at it though.

[k8s-ci-robot]

@SidakM: Reiterating the mentions to trigger a notification:
@kubernetes/sig-apps-feature-requests

In response to this:

Hey @claurence ,
Was waiting for a review from @kubernetes/sig-apps-feature-requests . Not sure when one of them will look at it though.

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.

[claurence]

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

[SidakM-zz]

@claurence Someone looked and commented but didn't follow up after so I am unsure where its at.

[claurence]

@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

[delgod]

@claurence it is critical functionality for stateful applications like databases.
If your run databases - you must to use StatefulSet.
so currently, PVC resize feature is mostly useless without StatefulSet resize.
please include it to 1.14 milestone.

[claurence]

@delgod because we have passed enhancement freeze and the KEP still is not merged please submit an exception request.

[chino]

Can we see something similar for DaemonSets?

[kacole2]

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.

[justaugustus]

/assign @SidakM

[SidakM-zz]

@gnufied Can we get this in for 1.15?

[evillgenius75]

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.

[archetec]

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!

[harshanarayana]

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

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

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

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[blafry]

/remove-lifecycle stale

[ialidzhikov]

/lifecycle frozen

[R-Studio]

@harshanarayana any news on this?

[KlavsKlavsen]

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]

It's going to be really helpful

[harshanarayana]

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]

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]

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