-
Feature
-
Resolution: Unresolved
-
Normal
-
None
Feature Overview (aka. Goal Summary)
Does away with the image setting in SD and gets the right marketplace image
Requirements (aka. Acceptance Criteria):
On ARO/HCP, the image is retrieved from the defaults in the release.
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 | managed |
| Classic (standalone cluster) | no |
| Hosted control planes | yes |
| Multi node, Compact (three node), or Single node (SNO), or all | All ARO/HCP supported configurations |
| Connected / Restricted Network | All ARO/HCP supported configurations |
| Architectures, e.g. x86_x64, ARM (aarch64), IBM Power (ppc64le), and IBM Z (s390x) | All ARO/HCP supported configurations |
| Operator compatibility | N/A |
| Backport needed (list applicable versions) | 4.18.z and 4.17.z |
| UI need (e.g. OpenShift Console, dynamic plugin, OCM) | N/A |
| Other (please specify) |
Out of Scope
Self-managed Azure HCP
- links to
