✨ Allocate dedicated host when a dedicated host doesn't exist

[rvanderp3]

What type of PR is this?

/kind feature

What this PR does / why we need it:

Builds on #5548 to enable CAPA to allocate a dedicated host. This removes the requirement that a dedicated host exist prior to instance provisioning. A core assumption of this PR is that there is a 1:1 mapping between an instance and the dedicated host on which it runs. Nothing in this implementation precludes scheduling multiple instances to a given dedicated host, but that is not the goal of this initial implementation.

Special notes for your reviewer:

Checklist:

• squashed commits
• includes emoji in title
• adds unit tests

Release note:

Adds support for provisioning an instance on a new dedicated host.

[k8s-ci-robot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[k8s-ci-robot]

Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

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-sigs/prow repository.

[punkwalker]

Hi @rvanderp3,
Thank you for picking this up.
I know the PR is still in draft but I wanted to add some suggestion at the start. Hope you don't mind.

[rvanderp3]

Hi @rvanderp3, Thank you for picking this up. I know the PR is still in draft but I wanted to add some suggestion at the start. Hope you don't mind.

not at all, I appreciate the early feedback

[enxebre]

covers #5599

[enxebre]

@rvanderp3 thanks! this is looking great. I dropped some early feedback.

[damdo]

/assign @damdo @nrb

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from nrb. For more information see the Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[rvanderp3]

/hold

investigating test failures

[k8s-ci-robot]

@rvanderp3: 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
pull-cluster-api-provider-aws-apidiff-main	55b4aca	link	false	/test pull-cluster-api-provider-aws-apidiff-main

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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-sigs/prow repository. I understand the commands that are listed here.

[rvanderp3]

after conferring with my team, it sounds like the apidiff error may be expected due to changes to the API. dropping the hold and ready for review.

[rvanderp3]

/unhold