The following is the end goal for feature gates in the CAPI operator:

ClusterAPIMachineManagement:

• Install all CAPIO manifests
• Run ClusterOperator-controller (IIUC hard requirement if we install manifests, or we'll block install)

ClusterAPIMachineManagementFoo and current platform is Foo, runs the following controllers:

• capiinstaller/installer/revision
• corecluster/infracluster
• kubeconfig
• secretsync

MachineAPIMigration should not directly gate any functionality.

MachineAPIMigrationFoo (and implicitly ClusterAPIMachineManagementFoo) and current platform is Foo, runs the following controllers:

• machine(set)?migration
• machine(set)?sync

The complete set of required platform-specific feature gates for the CAPI Operator is:

• ClusterAPIMachineManagementAWS
• ClusterAPIMachineManagementAzure
• ClusterAPIMachineManagementBareMetal
• ClusterAPIMachineManagementGCP
• ClusterAPIMachineManagementOpenStack
• ClusterAPIMachineManagementPowerVS
• ClusterAPIMachineManagementVSphere
• MachineAPIMigrationAWS
• MachineAPIMigrationAzure
• MachineAPIMigrationBareMetal
• MachineAPIMigrationGCP
• MachineAPIMigrationOpenStack
• MachineAPIMigrationPowerVS
• MachineAPIMigrationVSphere                                                                                                                                               

This story will be complete when the capi-operator endpoint specifically gates ClusterOperator and the various installer controllers correctly.