-
Epic
-
Resolution: Done
-
Major
-
None
-
CAPO supports essential installer scenarios
-
Strategic Product Work
-
False
-
None
-
False
-
Not Selected
-
To Do
-
OCPSTRAT-1002 - Remove Terraform from the OpenStack installer-TP
-
OCPSTRAT-1002Remove Terraform from the OpenStack installer-TP
-
0% To Do, 0% In Progress, 100% Done
Goal
- Implement scenarios in CAPO that can't be worked around on the installer with direct calls to OpenStack API.
Why is this important?
- Intermediate, testable deliverable on the path to installer integration.
- Ultimately required for installer integration.
- We do not currently intend to support this feature. CAPO will be self-managed only.
Scenarios
- User installs OpenShift with CAPO enabled.
- User deploys CAPI templates in a private namespace which deploy a separate workload OpenShift cluster on OpenStack.
Acceptance Criteria
- CI - MUST be running successfully with tests automated
- Release Technical Enablement
- ...
Dependencies (internal and external)
- ...
Previous Work (Optional):
- …
Open questions::
- …
- depends on
-
OSASINFRA-3207 Integrate CAPO into cluster-capi-operator (TP)
- Closed
- is depended on by
-
OSASINFRA-3379 Upstream CAPO release v0.10
- Closed
-
OSASINFRA-3254 CAPO is functionally equivalent to terraform
- Closed
-
OSASINFRA-3366 Bump capo-integration branch to new upstream release
- Closed