-
Feature
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
None
Feature Overview
- OpenShift will soon be fully capable of support for mixed architecture clusters, be that via HyperShift or the Heterogeneous work. To enable these technologies a heterogeneous payload is required and this Feature is to track the requirements/actions needed to move to only shipping heterogeneous payloads. This will facilitate maximum flexibility for the end user while minimizing disruption by having to change to the heterogeneous payload. It may also have the advantage of streamlining our test environments.
Goals
- Identify and contact all groups that will be effected by this change and seek feedback
- Assess impact from both a technical and customer perspective, for example what impact would having a bigger payload image have on our disconnected customers?
- Formulate a plan and get sign off on that plan from all necessary parties
Requirements
| Requirement | Notes | isMvp? |
|---|---|---|
| CI - MUST be running successfully with test automation | This is a requirement for ALL features. | YES |
| Heterogeneous payload is the default payload for OpenShift | YES | |
| Release Technical Enablement | Provide necessary release enablement details and documents. | YES |
| Imageregistry and Imagestreams support manifestlists | YES | |
| Openshift Builds needs to support creating manifestlisted images | needed to fulfill CI needs if heterogeneous is to be the only payload | YES |
| sparse manifestlist support in quay | needed for disconnected installs so customers don't incur the cost of mirroring extra arches | YES |
(Optional) Use Cases
This Section:
- Main success scenarios - high-level user stories
- Alternate flow/scenarios - high-level user stories
- ...
Questions to answer…
- What is the impact for infrastructure and SRE teams? Can they meet the SLOs for all architecture build pipelines
- How do we phase out single arch payloads?
- Do we have telemetry data to identify which clusters are truly multi architecture and not a single arch cluster running a heterogeneous payload
- Do we need all the functionality implemented in https://github.com/openshift/enhancements/blob/master/enhancements/multi-arch/heterogeneous-architecture-clusters.md before we can make heterogeneous the default payload? if not what is the minimum subset?
- What are the considerations for upgrades if there is only one graph going forward and how will it work
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
- How will increased payload size effect our customers?
Documentation Considerations
Questions to be addressed:
- What educational or reference material (docs) is required to support this product feature? For users/admins? Other functions (security officers, etc)?
- Does this feature have doc impact?
- New Content, Updates to existing content, Release Note, or No Doc Impact
- If unsure and no Technical Writer is available, please contact Content Strategy.
- What concepts do customers need to understand to be successful in [action]?
- How do we expect customers will use the feature? For what purpose(s)?
- What reference material might a customer want/need to complete [action]?
- Is there source material that can be used as reference for the Technical Writer in writing the content? If yes, please link if available.
- What is the doc impact (New Content, Updates to existing content, or Release Note)?
