While configuring the various CAPI infrastructure providers within OpenShift, we will by default have a large surface area of APIs and features that we do not necessarily want to support or install.

We need to go through each provider and determine:

• What is the minimum API surface that we need to expose?
• What is the minimum set of controllers that we need to run from the provider?
• Determine how to disable controllers/API surface within our existing operator patterns
• Determine if any of the elements we may disable, are required for MCE/HCP and therefore may want to be configured to be turned back on

In particular, as an example, this would mean that we do not, by default, ship EKS or ROSA functionality built into CAPA.

CC decarr who raised this during the CAPI F2F in July '24

DoD:

• Produce a document explaining an approach to achieve this.

• Make Jira cards