feat: Adding Pod Identity / Access Entries option for Karpenter #400
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.
What does this PR do?
Enables Pod Identity and Access Entry feature for Karpenter addon.
kube-system
, as recommended since v0.33TO DO: Change the "aws-ia/eks-blueprints-addon/aws" to the version supporting Pod Identity,
pre-commit
checks will not pass without that.Motivation
Pod Identity and Access Entries aims to be the default options for granting permissions to addons. We should adopt this in the v2.
More
pre-commit run -a
with this PRFor Moderators
Additional Notes