-
Feature
-
Resolution: Unresolved
-
Normal
-
None
Feature Overview (aka. Goal Summary)
- To validate the multiarch-tuning-operator can work on Hypershift (managed and management clusters
- To validate the multiarch-tuning-operator can work on Hypershift-based managed offerings
Goals (aka. expected user outcomes)
- Enable seamless use of the multiarch payload by default in several scenarios (managed services, rosa hcp, hypershift management clusters with mixarch workers when they handle single-arch hosted clusters)
- https://issues.redhat.com/browse/HOSTEDCP-1902
Requirements (aka. Acceptance Criteria):
1. [hypershift management cluster] handle single-arch amd64 and single-arch arm64 managed clusters from the same management cluster
2. [hypershift managed cluster with mixarch nodepools] same scenario as the classic one for OCP (user-wide)
Anyone reviewing this Feature needs to know which deployment configurations that the Feature will apply to (or not) once it's been completed. Describe specific needs (or indicate N/A) for each of the following deployment scenarios. For specific configurations that are out-of-scope for a given release, ensure you provide the OCPSTRAT (for the future to be supported configuration) as well.
| Deployment considerations | List applicable specific needs (N/A = not applicable) |
| Self-managed, managed, or both | Y |
| Classic (standalone cluster) | Y |
| Hosted control planes | Y |
| Multi node, Compact (three node), or Single node (SNO), or all | Y |
| Connected / Restricted Network | Y |
| Architectures, e.g. x86_x64, ARM (aarch64), IBM Power (ppc64le), and IBM Z (s390x) | Arm and x86 initially |
| Operator compatibility | N |
| Backport needed (list applicable versions) | N |
| UI need (e.g. OpenShift Console, dynamic plugin, OCM) | N |
| Other (please specify) | n/a |
Use Cases (Optional):
Include use case diagrams, main success scenarios, alternative flow scenarios. Initial completion during Refinement status.
<your text here>
Questions to Answer (Optional):
Include a list of refinement / architectural questions that may need to be answered before coding can begin. Initial completion during Refinement status.
<your text here>
Out of Scope
High-level list of items that are out of scope. Initial completion during Refinement status.
<your text here>
Background
Provide any additional context is needed to frame the feature. Initial completion during Refinement status.
<your text here>
Customer Considerations
Provide any additional customer-specific considerations that must be made when designing and delivering the Feature. Initial completion during Refinement status.
<your text here>
Documentation Considerations
Provide information that needs to be considered and planned so that documentation will meet customer needs. If the feature extends existing functionality, provide a link to its current documentation. Initial completion during Refinement status.
<your text here>
Interoperability Considerations
Which other projects, including ROSA/OSD/ARO, and versions in our portfolio does this feature impact? What interoperability test scenarios should be factored by the layered products? Initial completion during Refinement status.
<your text here>
