-
Epic
-
Resolution: Done
-
Critical
-
ACM 2.12.0, MCE 2.7.0
-
Test ACM add-ons with hosted clusters
-
False
-
None
-
False
-
Not Selected
-
To Do
-
0% To Do, 0% In Progress, 100% Done
Epic Goal
- Context:
Created this epic to track effort against making sure ACM add-ons work as expected with HCP type clusters.
This effort was co-ordinated and opened on behalf of ACM PM (bweidenb@redhat.com ) and Hypershift add-on dev lead (rokejungrh)
- Although we test the cluster lifecycle of hypershift across different providers - Agent, Kubevirt, AWS, IBM Power / Z - there is still an untested gap: ACM add-ons on hypershift clusters.
- ACM has several different component add-ons that automatically get installed on managed clusters in ACM that we need to ensure works as expected, along with our CLC coverage:
- Application
- Governance (policy)
- Search/Observability
Why is this important?
- Customers with ACM using hosted clusters with get ACM add-ons on those hosted clusters, we need to ensure they work as expected.
- IBM Power & Z move closer to GA for hosted control planes
Scenarios
- IBM team deploys ACM hub + a self-managed hosted cluster on IBM Z
- ACM CI QE will trigger all component tests against the hosted cluster
- ACM QE will triage any issues that appear
- Repeat 1-3 with a hosted cluster on IBM Power
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 - Downstream documentation merged: <link to meaningful PR>