feat: Add capacity reservation permissions to Karpenter IAM policy #3318
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…pacity-reservation permission as part of Karpenter version 1.3.0
Description
Karpenter version 1.3.0 now has a feature that allows for On Demand Capacity Reservation Support. The policy attached to the KarpenterController needs to be updated to allow this. More info can be found here: https://github.com/aws/karpenter-provider-aws/releases/tag/v1.3.0
Motivation and Context
As part of this update, the AllowScopedEC2InstanceAccessActions policy needs to be updated to allow for Capacity Reservations to be made through Karpenter. Karpenter have updated their docs for this see - https://github.com/aws/karpenter-provider-aws/pull/7801/files
Breaking Changes
No breaking changes
How Has This Been Tested?
examples/*
projectspre-commit run -a
on my pull request