-
Feature
-
Resolution: Unresolved
-
Critical
-
None
-
None
-
None
-
BU Product Work
-
False
-
-
False
-
100% To Do, 0% In Progress, 0% Done
-
0
-
Backlog Refinement
Feature Overview (aka. Goal Summary)
Add support for listing Marketplace Images in the RHCOS stream
Goals (aka. expected user outcomes)
Create a process/workflow for publishing marketplace images & updating stream
Requirements (aka. Acceptance Criteria):
OpenShift Installer to default to marketplace-image-based installs for Azure, which dramatically improves install time
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 | |
| Classic (standalone cluster) | |
| Hosted control planes | |
| Multi node, Compact (three node), or Single node (SNO), or all | |
| Connected / Restricted Network | |
| Architectures, e.g. x86_x64, ARM (aarch64), IBM Power (ppc64le), and IBM Z (s390x) | |
| Operator compatibility | |
| Backport needed (list applicable versions) | |
| UI need (e.g. OpenShift Console, dynamic plugin, OCM) | |
| Other (please specify) |
Background
Allows users to simply set a flag to use marketplace images, rather than needing to hunt down image details in documentation
Deduplicates effort between ARO & other teams that need marketplace images
Documentation Considerations
Usual documentation for the Installer on how to consume the feature will be required
Interoperability Considerations
This will be used by both self-managed and managed (ARO) customers
