-
Feature
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
False
-
None
-
False
-
Not Selected
Feature Overview
MCE has been building and shipping the hypershift operator from a release specific branch in order to pin a specific version of the hypershift operator with a MCE y version. For example, MCE 2.7 and its z-stream builds and ships the hypershift operator from its 4.17 branch.
This feature is to build and ship the hypershift operator from the main branch regardless of the MCE version.
Goals
- Simplify the hypershift operator test effort
- Simplify the hypershift operator development effor
- Eliminate having to backport code changes from main to multiple branches in the hypershift operator repo
Requirements
| Requirement | Notes | isMvp? |
|---|---|---|
| CI - MUST be running successfully with test automation | This is a requirement for ALL features. |
YES |
| Release Technical Enablement | Provide necessary release enablement details and documents. |
YES |
| Hypershift APIs must be backward compatible, reliable and consistent | https://issues.redhat.com/browse/HOSTEDCP-1979 |
(Optional) Use Cases
This Section:
- Main success scenarios - high-level user stories
- Alternate flow/scenarios - high-level user stories
- ...
Questions to answer
- This means the hypershift operator could be 2 versions ahead of MCE's OCP version.
- You could deploy n+2 managed hosted clusters
Out of Scope
- ...
Background, and strategic fit
This Section: What does the person writing code, testing, documenting
need to know? What context can be provided to frame this feature?
Assumptions
- ...
Customer Considerations
- ...
QE Considerations
Questions to be addressed:
- Deploying n+2 managed hosted clusters?
Documentation Considerations
Questions to be addressed:
- We might have to document clearly that there is a soft limit on the version of hosted clusters where n+2 hosted clusters are not supported.
- is depended on by
-
-
- New
-