Epic Goal
- looking from a design point of view
Why is this important?
- Installing/Uninstalling Operators is a frequent task. We are promoting installing Operators with OLM
Scenarios
- Create a Policy to install Operator with settings to remove resources once Policy gets deleted
- Delete the Policy and ensure everything is cleaned.
Acceptance Criteria
- CI - MUST be running successfully with tests automated
- Release Technical Enablement - Provide necessary release enablement details and documents.
- Design is ready
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>
- clones
-
ACM-1156 ACM OLM integration improvements (2.10)
-
- Closed
-
