-
Notifications
You must be signed in to change notification settings - Fork 135
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Align Karpenter IAM permissions with current permission guidance from Karpenter project #286
Comments
This issue has been automatically marked as stale because it has been open 30 days |
It's been some time, The process seems to now be to generate a policy template for the Karpenter version specified, following steps 7 & 8.
This produced the following $POLICY_DOCUMENT:
This varies quite a bit from the template of permissions that the blueprints-addons produces, there needs to be a catch-up:
Comparing the two, it seems the only missing permissions are for snapshots:
But there's a big difference in how the blueprints-addons creates broad account-wide statements for it's policy where the generated one from Karpenter utilizes conditions and numerous statements to create a least privilege access policy. |
Community Note
What is the outcome that you are trying to reach?
Describe the solution you would like
Describe alternatives you have considered
Additional context
The text was updated successfully, but these errors were encountered: