Epic Goal*

With this epic requests to report the PVs LastPhaseTransitionTime as a metric (value would be epoch timestamp in seconds).

Why is this important? (mandatory)

This will help our customers in their OCP storage management and costs reduction.
Use Case: PVs LastPhaseTransitionTime  metric would allow to identify PVs that their PVCs were deleted but have "Retain" policy(do not delete PV when PVC is deleted).
This would provide a way to know for how long this PV was not bound to a PVC. which in turns means it has not been used by a pod but a limited case.
  
Scenarios (mandatory) 

Provide details for user scenarios including actions to be performed, platform specifications, and user personas.  

1. As a system admin I want a report that will show me unused PVs that were not mounted, used and owned by anyone, so that I can decide if I want to delete them and free up storage space.

 
Dependencies (internal and external) (mandatory)

What items must be delivered by other teams/groups to enable delivery of this epic. 

Contributing Teams(and contacts) (mandatory) 

Our expectation is that teams would modify the list below to fit the epic. Some epics may not need all the default groups but what is included here should accurately reflect who will be involved in delivering the epic.

• Development - 
• Documentation -
• QE - 
• PX - 
• Others -

Acceptance Criteria (optional)

Provide some (testable) examples of how we will know if we have achieved the epic goal.  

Drawbacks or Risk (optional)

Reasons we should consider NOT doing this such as: limited audience for the feature, feature will be superseded by other work that is planned, resulting feature will introduce substantial administrative complexity or user confusion, etc.

Done - Checklist (mandatory)

The following points apply to all epics and are what the OpenShift team believes are the minimum set of criteria that epics should meet for us to consider them potentially shippable. We request that epic owners modify this list to reflect the work to be completed in order to produce something that is potentially shippable.

• CI Testing -  Basic e2e automationTests are merged and completing successfully
• Documentation - Content development is complete.
• QE - Test scenarios are written and executed successfully.
• Technical Enablement - Slides are complete (if requested by PLM)
• Engineering Stories Merged
• All associated work items with the Epic are closed
• Epic status should be “Release Pending”