Epic Goal
- For OPP Integration there is also the need for good documentaton. This Jira tracks our continuous effort to improve this
https://docs.google.com/document/d/1Y6gnDzKYaL_uL4ryiaVRS_Gq-uGDh_oZNYXS41id13Q/edit#
e.g. we need to improve our Sizing Requirements
Why is this important?
We need to highlight our integration efforts
documentation is especially required on:
- sizing
- what components run on the infra nodes
- taints and tolerations
- fine tuning
- backup of OPP+
- big items like cert-manager, prometheus, thanos, redis...
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>
- is cloned by
-
ACM-1278 ACM make PolicySet for OpenShift Plus stable
- Closed