-
Epic
-
Resolution: Done
-
Major
-
None
-
None
-
Azure: Document installing OpenShift in a restricted network
-
BU Product Work
-
Green
-
Done
-
OCPSTRAT-603 - Azure and Azure Stack Hub disconnected deployments
-
OCPSTRAT-603Azure and Azure Stack Hub disconnected deployments
-
0% To Do, 0% In Progress, 100% Done
-
-
ARO
Goal:
As an administrator, I would like to deploy OpenShift 4 clusters to Azure in a restricted network.
Problem:
Customers would like to install OpenShift on Azure using either a corporate proxy or local container image registry. This process is documented for AWS, GCP, VMware, and Bare Metal providers, but has not be documented for Azure.
Why is this important:
- Many of our customers leverage either a corporate proxy to access the internet or deploy clusters in restricted environments. This process needs to be documented for Azure like it is for the rest of the providers.
Lifecycle Information:
- Core
Previous Work:**
- Cluster-wide proxy enablement
- Disconnected Deployments
- https://docs.openshift.com/container-platform/4.3/installing/installing_aws/installing-restricted-networks-aws.html
Dependencies:
Prioritized epics + deliverables (in scope / not in scope):
- Document how to deploy an OpenShift cluster on Azure using offline content hosted in an local container image registry
- Document how to deploy an OpenShift cluster using a corporate proxy server to access the internet
Estimate (XS, S, M, L, XL, XXL):
Customers: North America Public Sector and Government Agencies, FSI, and many others
Open Questions: