Report last used time on a PVC

[gnufied]

Enhancement Description

• Report when a PVC was last used in pvc.Status
• Kubernetes Enhancement Proposal:
• Discussion Link:
• Primary Contact(assignee):
  • @RomanBednar
  • @gnufied
• Responseible SIGs:
  • sig-storage
• PRs by stage and milestone:
  • Alpha - v1.35
    • KEP (k/enhancements) update PR(s): KEP-5541: PersistentVolumeClaim Last Used Time #5795
    • Code (k/k) update PR(s): Report PVC unused time via PVC condition kubernetes#137862
    • Docs (k/website) update PR(s): Placeholder KEP-5541: Report Last Used Time on a PVC website#54553
  • Beta - v1.37
    • KEP (k/enhancements) update PR(s): KEP-5541: Update PersistentVolumeClaimUnusedSinceTime KEP for beta in 1.37 #6144
    • Code (k/k) update PR(s): Promote PersistentVolumeClaimUnusedSinceTime to Beta kubernetes#139620
    • Docs (k/website) update(s): promote PersistentVolumeClaimUnusedSinceTime to beta in 1.37 website#56085

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]

/sig storage
/milestone v1.35
/stage alpha

[k8s-ci-robot]

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

Details

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.

[sunnylovestiramisu]

Report when a VAC(not PVC?) was last used in pvc.Status

[aibarbetta]

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, and milestone struct 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!

[whtssub]

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

[k8s-ci-robot]

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

Details

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.

[k8s-ci-robot]

@whtssub: Can not set label tracked/no: Must be member in one of these teams: [release-team-enhancements release-team-leads]

Details

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.