-
Spike
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
BU Product Work
-
5
-
False
-
None
-
False
-
OCPSTRAT-1579 - Integrate Cluster API (CAPI) in standalone OCP-Phase 3
-
-
-
CLOUD Sprint 262, CLOUD Sprint 269
By default, an OpenShift cluster on AWS will only install the AWS CAPI infrastructure provider.
We have use cases (eg via MCE) where there is a want to install additional providers, and, have those act upon multiple namespaces.
We need to understand:
- What impacts will there be if we enable multiple providers?
- What will the configuration API look like to enable this?
- Can we enable controllers to act across multiple namespaces based on some configuration?
- Do we need to have configuration to enable subsets of provider functions, eg ROSA HCP provider inside CAPA
- How do we make sure the external platforms are not excluded in this API? (future expansion)
Expected outcome is an enhancement style document
CC rh-ee-smodeel who raised this during the CAPI F2F July '24
- is blocked by
-
OCPCLOUD-2689 Reduce scope of CAPI providers by default
-
- To Do
-