enhancements
enhancements copied to clipboard
Auto remove PVCs created by StatefulSet
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 1.32
- [x] Beta
- [x] KEP (
k/enhancements) update PR(s): https://github.com/kubernetes/enhancements/pull/3800 - [x] Code (
k/k) update PR(s):- https://github.com/kubernetes/kubernetes/pull/116501
- [x] Docs (
k/website) update(s):- https://github.com/kubernetes/website/pull/39926
- https://github.com/kubernetes/website/pull/39819
- [x] KEP (
- [ ] Stable
- [x] KEP (
k/enhancements) update PR(s): https://github.com/kubernetes/enhancements/pull/4901 - [ ] Code (
k/k) update PR(s): - [ ] Docs (
k/website) update(s):
- [x] KEP (
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
@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.
/sig storage
/assign
@kubernetes/sig-storage-feature-requests
@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.
CC @dsu-igeek
Having discussions with @dsu-igeek @msau42 @mattcary Should have a KEP with the proposal in shortly.
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
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
As per https://github.com/kubernetes/enhancements/pull/1915#issuecomment-698445762
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
/milestone v1.20
Hi @kk-src :wave:!
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
implementablestate.- It's
provisionalat the moment.
- It's
- 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!
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.
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
/remove-lifecycle stale
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
Hi @mattcary
Enhancements Freeze is 2 days away, Feb 9th EOD PST
Enhancements team is aware that KEP update is currently in progress (PR https://github.com/kubernetes/enhancements/pull/2440). Please make sure PR merges before the freeze. For PRR related questions or to boost the PR for PRR review, please reach out in slack #prod-readiness
Any enhancements that do not complete the following requirements by the freeze will require an exception.
- [IN PROGRESS] The KEP must be merged in an implementable state
- [IN PROGRESS] The KEP must have test plans
- [IN PROGRESS] The KEP must have graduation criteria
- [IN PROGRESS] The KEP must have a production readiness review
With PR https://github.com/kubernetes/enhancements/pull/2440 merged, this enhancement has met all the requirements for the enhancements freeze 👍
Greetings @mattcary @kk-src, Since your Enhancement is scheduled to be in 1.21, please keep in mind the important upcoming dates: • Tuesday, March 9th: Week 9 - Code Freeze • Tuesday, March 16th: Week 10 - Docs Placeholder PR deadline • If this enhancement requires new docs or modification to existing docs, please follow the steps in the Open a placeholder PR doc to open a PR against k/website repo. As a reminder, please link all of your k/k PR(s) and k/website PR(s) to this issue so we can track them. Thanks!
Docs placeholder PR: https://github.com/kubernetes/website/pull/26683
Greetings @mattcary @kk-src,
A friendly reminder that Code freeze is 5 days away, March 9th EOD PST Any enhancements that are NOT code complete by the freeze will be removed from the milestone will require an exception to be added back. Please also keep in mind that if this enhancement requires new docs or modification to existing docs, you'll need to follow the steps in the Open a placeholder PR doc to open a PR against k/website repo by March 16th EOD PST. Thanks!
Hi @mattcary, with code freeze now in effect, we are removing this enhancement from 1.21 release due to https://github.com/kubernetes/kubernetes/pull/99378 and https://github.com/kubernetes/kubernetes/pull/99728 not being merged or approved.
Feel free to file an exception to add this back into the release. thanks!
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten
/lifecycle frozen
Enhancement issues opened in kubernetes/enhancements should never be marked as frozen.
Enhancement Owners can ensure that enhancements stay fresh by consistently updating their states across release cycles.
/remove-lifecycle frozen
This implementation is under active development and should be able to go in after the 1.21 freeze is done.
/milestone v1.22
Hi @mattcary,
1.22 release team here. After reviewing the kep and approved PRR there's a few things that needs to be done before the 1.22 Enhancements Freeze which starts at 23:59:59 pst on Thursday, May 13:
- In the kep
README.md, update theTODOunder the Test Plan - In the kep.yaml, update the values of
latest-milestoneandalphamilestone to "v1.22". Update thebetaandstablemilestones accordingly
/sig apps
Thanks @reylejano!. PR created: https://github.com/kubernetes/enhancements/pull/2715