Feature Overview

This feature enables the OpenShift Installer (openshift-install) to support Installer-Provisioned Infrastructure (IPI) deployments on Azure VMware Solution (AVS). While OpenShift currently supports VMware vSphere and VMware Cloud (VMC), Azure AVS presents unique permission and security constraints. This enhancement ensures that the installer and the vSphere Cloud Services Interface (CSI) Driver can operate correctly within the AVS managed service.

Goals

• Automated Deployment: Provide a seamless IPI experience for customers migrating VMware workloads to Azure AVS.
• Storage Functional Parity: Ensure standard block storage operations (attach/detach, resize, snapshots) work out-of-the-box.
• Primary Persona: Cloud Architects and System Administrators looking to extend their VMware-based OCP footprint to Azure without adopting User-Provisioned Infrastructure (UPI) workflows.

Requirements

• Functional:
  • Support OpenShift on Azzur AVS using IPI installation method.

• Non-Functional:
  • Reliability: The vSphere CSI driver must maintain stability.
  • Usability: Documentation must clearly outline the differences in permissions between AVS and standard vSphere IPI.

Use Case

As a Cloud Infrastructure Engineer, I want to deploy an OpenShift cluster on Azure VMware Solution using the IPI method so that I can maintain a consistent deployment workflow across my hybrid cloud environment while benefiting from Azure's managed VMware infrastructure.

Questions to Answer

Out of Scope

• Zonal Deployments: AVS does not currently support the tagging/policy requirements for vSphere zonal distribution.

Links