Feature Overview (aka. Goal Summary)  

An elevator pitch (value statement) that describes the Feature in a clear, concise way.  Complete during New status.

Allow customers to see the PVC storage usage with CLI.

That way users can prevent that the volume is filling up and even take action before impact is happening on production level.

Goals (aka. expected user outcomes)

The observable functionality that the user now has as a result of receiving this feature. Include the anticipated primary user type/persona and which existing features, if any, will be expanded. Complete during New status.

Get how much space is used by a PVC with a oc get pvc

Requirements (aka. Acceptance Criteria):

A list of specific needs or objectives that a feature must deliver in order to be considered complete.  Be sure to include nonfunctional requirements such as security, reliability, performance, maintainability, scalability, usability, etc.  Initial completion during Refinement status.

This feature will show how much space is used by a volume by querying the PVC (not the PV), also this PVC has to active (mounted to a pod). As we are going to rely on a kubectl plugins that queries metrics, the volume has to be attached to a pod.

Anyone reviewing this Feature needs to know which deployment configurations that the Feature will apply to (or not) once it's been completed.  Describe specific needs (or indicate N/A) for each of the following deployment scenarios. For specific configurations that are out-of-scope for a given release, ensure you provide the OCPSTRAT (for the future to be supported configuration) as well.

Use Cases (Optional):

Include use case diagrams, main success scenarios, alternative flow scenarios.  Initial completion during Refinement status.

As an OCP admin I want to vizualise the storage consumed by active PVCs

As an OCP user/dev I want to vizualise or monitor/set alerts on PVCs that are becoming full

Questions to Answer (Optional):

Include a list of refinement / architectural questions that may need to be answered before coding can begin.  Initial completion during Refinement status.

Question answered in the initial spike - STOR-1852

Out of Scope

High-level list of items that are out of scope.  Initial completion during Refinement status.

Applies to PVC not PV

Applies to attached volume to running pods only

Background

Provide any additional context is needed to frame the feature.  Initial completion during Refinement status.

Although the metric is available it shouldn't require manual actions to see how much space is used by a PVC

Customer Considerations

Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.  Initial completion during Refinement status.

This is for attached PVC, customers may want to have this for any PVC which would require investigations and changes in the metrics' retentions policy.

Documentation Considerations

Provide information that needs to be considered and planned so that documentation will meet customer needs.  If the feature extends existing functionality, provide a link to its current documentation. Initial completion during Refinement status.

There should be RN entry as well as a short statement that mention the value to query to get the PVC usage value. Also mention that this applies to attached PVCs only

Interoperability Considerations

Which other projects, including ROSA/OSD/ARO, and versions in our portfolio does this feature impact?  What interoperability test scenarios should be factored by the layered products?  Initial completion during Refinement status.

There should not be any interoperability concerns.