-
Feature
-
Resolution: Unresolved
-
Major
-
None
-
None
-
Product / Portfolio Work
-
None
-
100% To Do, 0% In Progress, 0% Done
-
False
-
-
False
-
None
-
None
-
None
-
None
-
None
-
-
None
-
None
-
None
-
None
Feature Overview (aka. Goal Summary)
Report when a PVC was last used (timestamp)
Enhancement https://github.com/kubernetes/enhancements/issues/5541
Goals (aka. expected user outcomes)
Users & admins are interest to report when a PVC was last used in order to provide a list of "unused" volumes and take action; archive, backup, deleted, etc
Requirements (aka. Acceptance Criteria):
Expose a field that can be easily converted to a metric e.g in pvc.Status
| Deployment considerations | List applicable specific needs (N/A = not applicable) |
| Self-managed, managed, or both | both |
| Classic (standalone cluster) | yes |
| Hosted control planes | yes |
| Multi node, Compact (three node), or Single node (SNO), or all | all |
| Connected / Restricted Network | both |
| Architectures, e.g. x86_x64, ARM (aarch64), IBM Power (ppc64le), and IBM Z (s390x) | all |
| Operator compatibility | N/A |
| Backport needed (list applicable versions) | no |
| UI need (e.g. OpenShift Console, dynamic plugin, OCM) | no |
| Other (please specify) | no |
Out of Scope
Limited to PVC and is agnostic / not driver dependent
Background
OCP virt is intereted in this geature as virtualisation usually involves a lot of volumes and there are many case of unused volumes. To reduce cost they need a way to find old unused volumes.
See RFE-7922
Customer Considerations
Agnostic features, apply to all use cases. Ultimately it should be exposed as a metric.
Documentation Considerations
Document the new field
Interoperability Considerations
Agnostic
- is depended on by
-
-
- Approved
-
