Auto remove PVCs created by StatefulSet

[kk-src]

Enhancement Description

• One-line enhancement description (can be used as a release note):
  Auto remove PVCs created by StatefulSet

• Kubernetes Enhancement Proposal: KEP-1847: Auto remove PVCs created by StatefulSet.

• Primary contact (assignee): @mattcary

• Responsible SIGs: @sig-apps (with collaboration by @sig-storage)

• Enhancement target (which target equals to which milestone):

  • Alpha release target 1.23
  • Beta release target 1.27
  • Stable release target TBD

• Beta
  • KEP (k/enhancements) update PR(s):
  • Code (k/k) update PR(s):
    • Graduate StatefulSetAutoDelete to beta kubernetes#116501
  • Docs (k/website) update(s):
    • Update StatefulSet set docs for autodelete graduation to beta website#39926
    • Feature blog for StatefulSet Autodelete beta graduation website#39819

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

Resolves kubernetes/kubernetes#55045

[k8s-ci-robot]

@kk-src: The label(s) sig/sig-storage cannot be applied, because the repository doesn't have them

In response to this:

/sig sig-storage

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.

[kk-src]

/sig storage

[kk-src]

/assign

[pacoxu]

@kubernetes/sig-storage-feature-requests

[k8s-ci-robot]

@pacoxu: Reiterating the mentions to trigger a notification:
@kubernetes/sig-storage-feature-requests

In response to this:

@kubernetes/sig-storage-feature-requests

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.

[xing-yang]

CC @dsu-igeek

[kk-src]

Having discussions with @dsu-igeek @msau42 @mattcary
Should have a KEP with the proposal in shortly.

[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

[kikisdeliveryservice]

Hi @kk-src

Enhancements Lead here. Will there be any work for this in 1.20?

Also, as a reminder to be included in a release:

The KEP must be merged in an implementable state
The KEP must have test plans
The KEP must have graduation criteria.

Thanks
Kirsten

[kikisdeliveryservice]

As per #1915 (comment)

marking this is as tracked.

Please note that Enhancements Freeze is October 6th, by which time to be included in the milestone:
The KEP must be merged in an implementable state (not yet merged & provisional)
The KEP must have test plans (missing)
The KEP must have graduation criteria (missing)

Best,
Kirsten

[kikisdeliveryservice]

/milestone v1.20

[mikejoh]

Hi @kk-src 👋!

I'm one of the Enhancement shadows for the 1.20 release cycle. This is a friendly reminder that the Enhancement freeze is roughly one week from now on the 6th of October. I'm repeating the requirements needed by then:

• The KEP must be merged in an implementable state.
  • It's provisional at the moment.
• The KEP must have test plans.
  • Missing in the KEP.
• The KEP must have graduation criteria.
  • Also missing in the KEP.

Let us know if you have any questions etc.!

Thanks!

[mikejoh]

As a reminder, the Enhancements Freeze is Tomorrow October 6th EOD PST. All KEPs and updates must be merged by that time. After October 6th, you will need to request an Exception to be included in the 1.20 Release.

[kikisdeliveryservice]

Hi @kk-src

Enhancements Freeze is now in effect. Unfortunately, your KEP PR has not merged. If you wish to be included in the 1.20 Release, please submit an Exception Request as soon as possible.

Best,
Kirsten
1.20 Enhancements Lead

[kk-src]

/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-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[soltysh]

/milestone v1.27
/label lead-opted-in

[fsmunoz]

Hello @kk-src 👋, v1.27 Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00 PDT Thursday 9th February 2023.

This enhancement is targeting for stage beta for 1.27 (please correct me, if otherwise)

Here's where this enhancement currently stands:

• KEP readme using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable for latest-milestone: 1.27
• KEP readme has a updated detailed test plan section filled out
• KEP readme has up to date graduation criteria
• KEP has a production readiness review that has been completed and merged into k/enhancements.

For this KEP, we would need to update the following:

• Update to the latest template of the KEP.
• Update the PRR, namely there is a new question in Scalability about resource exhaustion.

The status of this enhancement is marked as at risk. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

[mattcary]

Thank you, I've created #3847 to update the KEP.

Note this KEP is tracked in the sig-apps project board. I'll try to update the label.

/tracked yes

[mattcary]

/tracked

[soltysh]

@mattcary the release team only has the power to mark KEP as tracked, they are continuously monitoring the KEPs, we just need to wait for @fsmunoz to re-visit this issue.

[mattcary]

Ah, thank you! I didn't realize.

[fsmunoz]

Thank you @mattcary ! The changes cover the previous points, but the markdown formatting seems off in the Scalability section: subheadings are cut short and the rest appears as text. Could you take a look? Thanks!

[mattcary]

Oops, thanks for catching that.

#3856

[fsmunoz]

@mattcary thank you!

• KEP readme using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable for latest-milestone: 1.27
• KEP readme has a updated detailed test plan section filled out
• KEP readme has up to date graduation criteria
• KEP has a production readiness review that has been completed and merged into k/enhancements.

This enhancement is ready to be traced for graduation to beta in v1.27.

/label tracked/yes

[Rishit-dagli]

Hi @kk-src 👋, I’m reaching out from the 1.27 Release Docs team. This enhancement is marked as ‘Needs Docs’ for the 1.27 release.

Please follow the steps detailed in the documentation to open a PR against dev-1.27 branch in the k/website repo. This PR can be just a placeholder at this time, and must be created by March 16. For more information, please take a look at Documenting for a release to familiarize yourself with the documentation requirements for the release.
Please feel free to reach out with any questions. Thanks!

[mattcary]

@Rishit-dagli is this not the right placeholder pr? kubernetes/website#39819

[msau42]

@mattcary there is also the k8s documentation that updates the feature gate table, user guide, etc.

[mattcary]

Done! kubernetes/website#39926

[fsmunoz]

Hi @kk-src , @mattcary 👋,

Checking in as we approach 1.27 code freeze at 17:00 PDT on Tuesday 14th March 2023.

Please ensure the following items are completed:

• All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
• All PRs are fully merged by the code freeze deadline.

For this enhancement, it looks like the following PRs need to merge:

• Graduate StatefulSetAutoDelete to beta kubernetes#116501

This is based on information shared here, given the inability of the lead to change the issue description.

Please let me know what other PRs in k/k I should be tracking for this KEP.

As always, we are here to help should questions come up. Thanks!

[mattcary]

Hi, I'm leading this bug, but don't have access to change the issue description.

The pending PR is kubernetes/website#39926.

[mattcary]

Oops, sorry that's the wrong PR. kubernetes/kubernetes#116501 is the right pending PR.

[fsmunoz]

@mattcary thank you, I've updated the status above.

[npolshakova]

Hi @carlory, Is this targeting 1.29? If it is, can you add the lead-opted-in label so that the enhancement is tracked? Thanks!

[mattcary]

sorry for missing this -- we're pushing this to 1.30 so we can collect more usage data, see #4197 (comment)