User Story

As a customer I want a way to supply metric data from my air-gapped OpenShift cluster so that I can use cost managmeent.

Prioritization / Business Case

• We have customers that want to use cost management but are not connected to the internet for easy sending of metric data.
• This tightens support for on-premise clusters

Out Of Scope

• Specifically call out things that should not be done in this epic

Impacts

• Operators
• Docs

External Dependencies

• AWS S3 maybe?

UX Requirements

• Is completion of a design/mock a prerequisite to working this epic or can portions be done concurrently?

UI Requirements

• Does the UI require a API contract with the backend so that UI could be developed prior to completing the API work?

Documentation Requirements

• This will be a documentation heavy epic once we determine how we want to achieve the end.

Backend Requirements

• Engineering is coming up with a method here
• The operator should be able to manage its own storage. Deleting old reports, configuring the storage time span (if the customer wants to upload the data once per month or once per quarter we should support at least 1 week more than the necessary 31 days or 92 days, let's say 40 or 100 days)

QE Requirements

• Will need to test an air-gapped cluster

Release Criteria

• Can this epic be released as individual issues/tasks are completed?
• Can the backend be released without the frontend?
• Has QE approved this epic?