Goal:

As an administrator, I would like to deploy OpenShift 4 clusters to an on-premise Azure Stack Hub environment leveraging installer-provisioned infrastructure.

Problem:

Customers were able to deploy to Azure Stack Hub in OCP 3.11, but our global configuration in OCP 4.1 doesn't support this.

Many customers will want a fully-automated deployment method, so we should try to deliver an installer-provisioned infrastructure workflow.

Why is this important:

• Many of our public sector customers would like to move off 3.11 and on to 4.1, but missing support for Azure Stack Hub will prevent them from being able to upgrading.

 
Lifecycle Information:

• Core

Previous Work:

Dependencies:

• Custom API endpoint support w/ CA
• Cloud / Machine API
• Image Registry
• Ingress
• Kube Controller Manager
• Cloud Credential Operator
• Storage
• others?

• Requires access to local Azure Stack Hub environment
• Working CI environment for GA product support

Prioritized epics + deliverables (in scope / not in scope):

• Allow on-premise Azure Stack Hub regions to be selected/specified for OpenShift cluster deployment
• Provide mechanism for defining custom API endpoints necessary for cluster deployment
• Enable customers to use their own managed internal/cluster DNS solutions due to provider and operational restrictions

Estimate (XS, S, M, L, XL, XXL): L

Customers: North America Public Sector and Government Agencies

Open questions: