features: add capi-installer gate per platform

[patrickdillon]

Adds a capi-installer feature gate for each platform.

/cc @JoelSpeed @deads2k

FYI:
@r4f4
@jhixson74
@bfournie
@cjschaef
@yanhua121
@stephenfin
@mjturek
@rvanderp3

[openshift-ci]

Hello @patrickdillon! Some important instructions when contributing to openshift/api:
API design plays an important part in the user experience of OpenShift and as such API PRs are subject to a high level of scrutiny to ensure they follow our best practices. If you haven't already done so, please review the OpenShift API Conventions and ensure that your proposed changes are compliant. Following these conventions will help expedite the api review process for your PR.

[r4f4]

So we'll need 2 feature gates to use a capi provider? ClusterAPIInstall and then ClusterAPIInstallAWS for AWS, e.g.

[JoelSpeed]

So we'll need 2 feature gates to use a capi provider? ClusterAPIInstall and then ClusterAPIInstallAWS for AWS, e.g.

I would expect it to be an or semantic. We want to start adding each of these to the TPNU set as they mature, but the original gate will stay for custom setups only.

@patrickdillon Do you have a PR for the installer that pairs with this?

[patrickdillon]

So we'll need 2 feature gates to use a capi provider? ClusterAPIInstall and then ClusterAPIInstallAWS for AWS, e.g.

I would expect it to be an or semantic. We want to start adding each of these to the TPNU set as they mature, but the original gate will stay for custom setups only.

@patrickdillon Do you have a PR for the installer that pairs with this?

+1 I did keep the original feature gate to enable for all platforms (would be fine to remove), but you can an enable individual platforms with a single platform. Opened: openshift/installer#8311

[JoelSpeed]

/lgtm

Scanned over the installer PR and seems like what I was expecting

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JoelSpeed, patrickdillon

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [JoelSpeed]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 29a704b and 2 for PR HEAD 7d9df7e in total

[openshift-ci]

@patrickdillon: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-azure	7d9df7e	link	false	/test e2e-azure

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD e1deb89 and 1 for PR HEAD 7d9df7e in total

[patrickdillon]

/skip

[openshift-bot]

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-cluster-config-api-container-v4.17.0-202404250047.p0.gcb0966a.assembly.stream.el9 for distgit ose-cluster-config-api.
All builds following this will include this PR.