kubernetes
Report last used time on a PVC
Enhancement Description
- Report when a PVC was last used in
pvc.Status - Kubernetes Enhancement Proposal:
- Discussion Link:
- Primary Contact(assignee):
- @ArvindParekh
- @gnufied
- Responseible SIGs:
- sig-storage
- PRs by stage and milestone:
- [ ] Alpha - v1.35
- [ ] KEP (
k/enhancements) update PR(s): - [ ] Code (
k/k) update PR(s): - [ ] Docs (
k/website) update PR(s):
- [ ] KEP (
- [ ] Alpha - v1.35
The use case is, many of our users are interested in data that, if a PVC is sitting unused. That is kinda hard to determine from outside since only kubernetes knows accurately when a PVC was used in a pod. For larger clusters this would make it possible for users to get rid of unused PVCs.
@gnufied: You must be a member of the kubernetes/milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your Milestone Maintainers Team and have them propose you as an additional delegate for this responsibility.
In response to this:
/sig storage /milestone v1.35 /stage alpha
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-sigs/prow repository.
Hello @gnufied 👋, v1.35 Enhancements team here.
This is a reminder of the upcoming PRR freeze on Thursday 9th October 2025 (AoE) / Friday 10th October 2025, 12:00 UTC.
This enhancement is targeting stage alpha for v1.35 (correct me, if otherwise)
Here's where this enhancement currently stands:
- [ ] PR open or merged with the KEP's PRR questionnaire filled out.
- [ ] PR open or merged with kep.yaml updated with the
stage,latest-milestone, andmilestonestruct filled out. - [ ] PR open or merged with a PRR approval file with the PRR approver listed for the stage the KEP is targeting.
For this KEP, we would just need to update the following:
- Open a PR to complete the items above
Note that the PRs are not required to be approved or merged by the PRR freeze deadline. Having the PRR questionnaire filled out by the deadline will help ensure that the PRR team has enough time to review your KEP before enhancements freeze on Thursday 16th October 2025 (AoE) / Friday 17th October 2025, 12:00 UTC. For more information on the PRR process, see here.
The status of this enhancement is marked as At risk for PRR freeze. Please keep the issue description up-to-date with appropriate stages as well.
If you anticipate missing PRR freeze, you can file an exception request in advance.
Thank you!
Hello @gnufied 👋, v1.35 Enhancements team here.
Unfortunately, this enhancement did not meet requirements for PRR freeze.
If you still wish to progress this enhancement in {current release}, please file an exception request as soon as possible, within three days. If you have any questions, you can reach out in the #release-enhancements channel on Slack and we'll be happy to help. Thanks!
/label tracked/no /milestone clear
@whtssub: You must be a member of the kubernetes/milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your Milestone Maintainers Team and have them propose you as an additional delegate for this responsibility.
In response to this:
Hello @gnufied 👋, v1.35 Enhancements team here.
Unfortunately, this enhancement did not meet requirements for PRR freeze.
If you still wish to progress this enhancement in {current release}, please file an exception request as soon as possible, within three days. If you have any questions, you can reach out in the #release-enhancements channel on Slack and we'll be happy to help. Thanks!
/label tracked/no /milestone clear
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-sigs/prow repository.
@whtssub: Can not set label tracked/no: Must be member in one of these teams: [release-team-enhancements release-team-leads]
In response to this:
Hello @gnufied 👋, v1.35 Enhancements team here.
Unfortunately, this enhancement did not meet requirements for PRR freeze.
If you still wish to progress this enhancement in {current release}, please file an exception request as soon as possible, within three days. If you have any questions, you can reach out in the #release-enhancements channel on Slack and we'll be happy to help. Thanks!
/label tracked/no /milestone clear
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-sigs/prow repository.
Report when a VAC(not PVC?) was last used in pvc.Status
No, I meant PVC not VAC. The use case is, many of our users are interested in data that, if a PVC is sitting unused. That is kinda hard to determine from outside since only kubernetes knows accurately when a PVC was used in a pod. For larger clusters this would make it possible for users to get rid of unused PVCs.
Hey @ArvindParekh 👋, This KEP looks interesting and I've a little background around storage as I have experience working on a CSI driver, let me know if you think we can collaborate!
Thanks!!
Count me in! Happy to help and collaborate on this. @ArvindParekh @kishen-v
Hi @gnufied 👋 v1.35 Enhancements Team here.
We are nearing the close of the v1.35 release. As part of the end of release cleanup, we are removing the lead-opted-in label to prepare for the next cycle.
If you would like this enhancement to be considered for the next release, please have the SIG lead opt in again by re adding the label and setting the appropriate milestone for the new release. This ensures the enhancement appears on the tracking board.
Thanks!
/remove-label lead-opted-in