Is your request related to a new offering from AWS?
No
Is your request related to a problem? Please describe.
In the past there was a problem with IAM policy reaching limits for clusters with long names.
Workaround was released for module (PR), but now Karpenter project split IAM policies in this PR, so I think workaround can be removed and module IAM sync with upstream.
Related issue in Karpenter repo aws/karpenter-provider-aws#7874 (comment)
Describe the solution you'd like.
Sync module IAM policies with upstream Karpenter - i.e. split them.
Describe alternatives you've considered.
Current workaround works, but I think would be better to eliminate issue with IAM policy size completely.
P.S. Workaround is enable_inline_policy = true
Additional context
I can try to create PR little bit later this week.
Is your request related to a new offering from AWS?
No
Is your request related to a problem? Please describe.
In the past there was a problem with IAM policy reaching limits for clusters with long names.
Workaround was released for module (PR), but now Karpenter project split IAM policies in this PR, so I think workaround can be removed and module IAM sync with upstream.
Related issue in Karpenter repo aws/karpenter-provider-aws#7874 (comment)
Describe the solution you'd like.
Sync module IAM policies with upstream Karpenter - i.e. split them.
Describe alternatives you've considered.
Current workaround works, but I think would be better to eliminate issue with IAM policy size completely.
P.S. Workaround is
enable_inline_policy = trueAdditional context
I can try to create PR little bit later this week.