-
Epic
-
Resolution: Unresolved
-
Major
-
ACM 2.16.0, MCE 2.11.0
-
None
-
AddOn Compliance Testing
-
Quality / Stability / Reliability
-
False
-
-
False
-
Not Selected
-
To Do
-
Important
OCP/Telco Definition of Done
https://docs.google.com/document/d/1TP2Av7zHXz4_fmeX4q9HB0m9cqSZ4F6Jd4AiVoaF_2s/edit#heading=h.gaa58bzbvwde
Epic Template descriptions and documentation.
https://docs.google.com/document/d/14CUCEg6hQ_jpsFzJtWo29GfFVWmun2Uivrxq3_Fkgdg/edit
ACM-wide Product Requirements (Top-level Epics)
https://docs.google.com/document/d/1uIp6nS2QZ766UFuZBaC9USs8dW_I5wVdtYF9sUObYKg/edit
*<--- Cut-n-Paste the entire contents of this description into your new
Epic --->*
Epic Goal
ACM includes many addOns developed by different teams. While they are all built on the addon-framework, not every addOn has implemented the full set of required features, such as:
- Minimum version of addon-framework
- Custom installation namespaces
- HTTP/HTTPS proxy configuration
- Custom node selectors and tolerations
- Custom image registries
- Resource requirement settings
- …
Currently, testing is handled individually by each addOn owner, which makes it difficult to ensure consistent feature coverage across all addOns in a given release.
To address this, we propose introducing AddOn compliance testing, driven by the Server Foundation team (maintainers of the addon-framework). This would produce a standardized compliance test report and ensure addOn owners address any identified gaps, improving overall quality and consistency.
The related upstream issue: https://github.com/open-cluster-management-io/ocm/issues/1148
Why is this important?
...
Scenarios
...
Acceptance Criteria
...
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 - Doc issue opened with a completed template. Separate doc issue
opened for any deprecation, removal, or any current known
issue/troubleshooting removal from the doc, if applicable. - Considerations were made for Extended Update Support (EUS)
