-
Feature
-
Resolution: Unresolved
-
Major
-
None
Feature Overview (aka. Goal Summary)
This feature aims to improve the reliability and integration of the e2e-aks test suite by deprecating outdated test configurations, and incorporating the updated suite into continuous integration (CI) workflows and release payload validation processes. This ensures ongoing compatibility, quality, and enforcement in ARO's hosted control plane (HCP) environments.
Goals (aka. expected user outcomes)
- Remove e2e-aks tests for OpenShift 4.18, as ARO HCP support is not being backported to this version.
- Integrate the e2e-aks tests as informing initially, and eventually as blocking, into the release payload controller.
- Ensure the e2e-aks tests are triggered as part of CI for new payloads.
- Improve release confidence for teams working with ARO on hosted AKS control planes.
Primary users:
- Release engineering teams
- QA and CI/CD pipeline maintainers
- ARO HCP development and support teams
Requirements (aka. Acceptance Criteria):
- e2e-aks 4.18 job is removed from test configuration.
- e2e-aks test suite is added as an informing job in release payload controller.
- CI system runs the e2e-aks tests against payloads.
- Process is in place to promote the job to blocking status based on stability.
Deployment considerations
| Scenario | Needs |
|---|---|
| Self-managed, managed, or both | Managed (ARO-specific) |
| Classic (standalone cluster) | N/A |
| Hosted control planes | Required |
| Multi node, Compact (three node), or Single node (SNO), or all | Multi-node only |
| Connected / Restricted Network | Connected only |
| Architectures | x86_64 and arm64 |
| Operator compatibility | Ensure compatibility with hypershift and relevant testing operators |
| Backport needed | N/A – ARO HCP not supported on 4.18 |
| UI need | N/A |
| Other | Ensure test results feed into release dashboards and status reporting |
Use Cases (Optional):
Main Scenario:
- A new OpenShift payload is built.
- CI runs the e2e-aks tests as informing.
- Based on stability, the tests are eventually made blocking.
- Release engineers can use this signal to gate ARO HCP-related releases.
Alternative Flow:
- If the tests fail intermittently, the team is alerted and issues are triaged before allowing the payload through blocking status.
Questions to Answer (Optional):
- What is the timeline for graduating informing → blocking?
- Are there any config changes needed in test-infra to support these integrations?
Out of Scope
- Adding new test coverage to e2e-aks (this is strictly cleanup and integration).
- Support for AKS in unsupported OpenShift versions (e.g., 4.18 and earlier).
- Broader test unification across non-AKS platforms.
Background
The e2e-aks tests were originally introduced to validate the ARO implementation on AKS using hosted control planes. With the decision not to backport HCP support to OpenShift 4.18, those specific tests are obsolete. At the same time, the stability and integration of these tests into CI and release gating is essential to ensuring the reliability of new releases.
Customer Considerations
ARO HCP customers depend on stability and release confidence for hosted clusters. This work ensures their payloads are tested appropriately and that regressions do not reach production environments.
Documentation Considerations
N/A
Interoperability Considerations
- This feature directly impacts ARO and Hypershift teams.
- Interoperability test scenarios with ROSA/OSD are out of scope.
- CI/test integration must continue to function with hypershift deployment models.
- links to
