-
Feature
-
Resolution: Unresolved
-
Major
-
None
-
None
-
BU Product Work
-
False
-
-
False
-
100% To Do, 0% In Progress, 0% Done
-
0
Feature Overview (aka. Goal Summary)
Add support to ND and NV machine series to be used on OpenShift deployment in Azure
Goals (aka. expected user outcomes)
As a user, I can deploy OpenShift in Azure using ND and NV machine series so both the Control Plane and Compute Nodes can run on these machine series
Requirements (aka. Acceptance Criteria):
ND and NV series can be selected at install time to be used to deploy OpenShift on Azure
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) |
Out of Scope
These machines series will be available for OpenShift to be used once they are declared GA by Microsoft
Background
GPU-enabled instances in the cloud have quite a lot of demand and customers need the assurance that these instances have been tested with OpenShift.
Documentation Considerations
Usual documentation to list these machine series as tested
Interoperability Considerations
This feature will be consumed by ARO later
- clones
-
-
- New
-
