-
Epic
-
Resolution: Done
-
Major
-
None
-
None
-
IBM Public Cloud: Support IPI deployment
-
installer
-
Done
-
OCPPLAN-5572 - IBM Public Cloud support (Tech Preview)
-
OCPPLAN-5572IBM Public Cloud support (Tech Preview)
-
0% To Do, 0% In Progress, 100% Done
Goal:
As an administrator, I would like to deploy OpenShift 4 on IBM Public Cloud leveraging best-practices, installer provisioned infrastructure.
Problem:
Customers would like to be able to easily and quickly deploy OpenShift 4 on other cloud providers rather than being locked into a select few.
Why is this important:
- This will enable more customers to make the move to OCP 4 by providing deployment support on other popular cloud providers.
- IPI deployment provides a simplified, best-practices OpenShift 4 deployment for customers by leveraging installer provisioned infrastructure objects and nodes enabling faster cluster bring-up time and significantly configurations errors.
- Automated installation process provides the framework for integrating into our CI system.
Dependencies (internal and external):
- RHCOS support + image publishing pipeline
- Machine API
- Image Registry Operator
- Ingress
- Kube Controller Manager
- Cloud Credential Operator
Prioritized epics + deliverables (in scope / not in scope):
- Terraform infrastructure config work
- Integration with IBM Cloud DNS and Load Balancer services
- Support for IBM Cloud Storage
- OpenShift CI system running on IBM Cloud infrastructure
Estimate (XS, S, M, L, XL, XXL):
Previous Work:
- ROKS enablement work
Customers:
Open questions:
- account is impacted by
-
OCPBUGS-6263 Unable to provision Bare Metal in IBM Cloud Gen 2 VPC
- Closed
- is related to
-
OCPBUGS-626 [IBMCloud] Worker nodes stuck in Provisioning during cluster creation - fail to join cluster
- Closed
-
OCPBUGS-539 [IBMCloud] Storage node labeler fails to label node for csi-driver
- Closed
- links to