✨ Capacity reservation preferences

[BraeTroutman]

What type of PR is this?

/kind feature

What this PR does / why we need it:

This PR adds support for the running of EC2 instances with capacity reservation preferences: that is, allowing an instance to be run to:

• specifically avoid using capacity reservations (even open ones)
• run only if the specified capacity reservation has room
• (default) run on demand, possibly taking up open capacity reservations if they have room

Which issue(s) this PR fixes *:
Fixes #5606

Special notes for your reviewer:

Checklist:

• squashed commits
• includes documentation
• includes emoji in title
• adds unit tests
• adds or updates e2e tests

Release note:

Support running EC2 instances with capacity reservation preferences. i.e. `capacityReservationPreference: none`

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: BraeTroutman / name: Brae Troutman (bc23ec5, a2d76a7, 108a81f, aa0e221)

[k8s-ci-robot]

Welcome @BraeTroutman!

It looks like this is your first PR to kubernetes-sigs/cluster-api-provider-aws 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/cluster-api-provider-aws has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @BraeTroutman. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[BraeTroutman]

/kind feature

[damdo]

/ok-to-test

[damdo]

/assign @damdo @nrb

[damdo]

linting checks are unhappy https://prow.k8s.io/view/gs/kubernetes-ci-logs/pr-logs/pull/kubernetes-sigs_cluster-api-provider-aws/5609/pull-cluster-api-provider-aws-test/1953719755814735872

[BraeTroutman]

linting checks are unhappy https://prow.k8s.io/view/gs/kubernetes-ci-logs/pr-logs/pull/kubernetes-sigs_cluster-api-provider-aws/5609/pull-cluster-api-provider-aws-test/1953719755814735872

Linter errors fixed locally: I'll leave the follow up commits here for tracking for now, and re-squash once we're satisfied with the state of things

[damdo]

/test pull-cluster-api-provider-aws-e2e-eks pull-cluster-api-provider-aws-e2e

[damdo]

/lgtm

Thanks @BraeTroutman !

/assign @nrb @richardcase @dlipovetsky @AndiDog

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: d9e9175240a9886d73446e666ef4502ca05d0d6f

[nrb]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: nrb

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [nrb]

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