-
Epic
-
Resolution: Done
-
Major
-
None
-
None
-
None
-
Scrape Profiles GA
-
False
-
None
-
False
-
Not Selected
-
NEW
-
To Do
-
-
NEW
-
100
-
100%
-
0
Epic Goal
- Scrape Profiles was introduced as Tech Preview in 4.13, goal it to now promote it to GA
- Scrape Profiles Enhancement Proposal should be merged
- OpenShift developers that want to adopt the feature should have the necessary tooling and documentation on how to do so
- OpenShift CI should validate if possible changes in profiles that might break a profile or cluster functionality
This has no link to a planing session, as this predates our Epic workflow definition.
Why is this important?
- Enables users to minimize the resrource overhead for Monitoring.
Scenarios
- ...
Acceptance Criteria
- CI - MUST be running successfully with tests automated
- Release Technical Enablement - Provide necessary release enablement details and documents.
- ...
Dependencies (internal and external)
- ...
Previous Work (Optional):
Open questions::
- …
Done Checklist
- CI - CI is running, tests are automated and merged.
- Release Enablement <link to Feature Enablement Presentation>
- 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 Polarion: <link or reference to Polarion>
- QE - Automated tests merged: <link or reference to automated tests>
- DOC - Downstream documentation merged: <link to meaningful PR>
