We don't use a feature gate for determining whether to deploy CAPO or not. Rather, we check for a whole feature set: specifically, the TechPreviewNoUpgrade. However, the MachineAPIMigration controller from cluster-capi-operator does use a feature gate, MachineAPIMigration, which is not included in the TechPreviewNoUpgrade feature set and must be enabled manually using the CustomNoUpgrade feature set. This leaves us in a bit of a catch-22. We can resolve this by ensuring CAPO is also deployed when the CustomNoUpgrade feature set is used.

See https://github.com/openshift/cluster-capi-operator/pull/238 for the changes to all the other controllers.