-
Epic
-
Resolution: Unresolved
-
Major
-
None
-
ACM 2.8.0, ACM 2.7.4
-
Hypershift Automation Backlog
-
False
-
None
-
False
-
Not Selected
-
To Do
-
48% To Do, 0% In Progress, 52% Done
Epic Goal
Develop a set of automated regression test to cover all scenarios in ACM that make use of Hypershift and cover the following testcases:
Why is this important?
Hypershift is a tech-preview feature in ACM 2.8 but will go GA as part of ACM 2.9 (most likely). QE should have a stable regression suite to cover the test scenarios.
Scope
- Daily pipeline to check the health of hypershift add-on
- SD-Hypershift (aka ROSA Hypershift) deployment method of hypershift add-on is not in scope.
- Only local-cluster (aka official ACM supported way) hypershift-addon is in scope.
- E2E tests will revolve around HyperShift add-on for AWS/kubevirt. BM to be tracked separately by Eco QE team.
- add-on e2e tests should test the functionality of hypershift cluster lifecycle: creating, maintaining (upgrades, node scaling), and destroying
- Created hypershift clusters need to be hooked into the full ACM E2E pipeline to test ACM add-ons on hypershift hosted clusters
Repo:
https://github.com/stolostron/hypershift-addon-e2e-tests/tree/main/e2e-go