EPIC Goal

We need to document how to use Resource optimization/cost management plugin so the users can understand how to use it.

Background/Feature Origin

We have existing documentation upstream but as the plugin is maturing we need to make sure we have official documentation.

Why is this important?

The users need to know how to use the plugin .

User Scenarios

As a user I would like to know how to optimize my OCP workload and track my costs.

Dependencies (internal and external)

The plugin relies on Red Hat insights backend running as part of console[dot] or on premise (in the future).

Acceptance Criteria

Release Enablement/Demo - Provide necessary release enablement details
and documents

DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
Issue>

DEV - Upstream documentation merged: <link to meaningful PR or GitHub
Issue>

DEV - Downstream build attached to advisory: <link to errata>

QE - Test plans in Playwright: <link or reference to playwright>

QE - Automated tests merged: <link or reference to automated tests>

DOC - Downstream documentation merged: <link to meaningful PR>