-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Pod Identity Association missing from Karpenter module #3029
Comments
3 tasks
This issue has been resolved in version 20.10.0 🎉 |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
More of a question - is there a reason
aws_eks_pod_identity_association
isn't in the Karpenter module? It looks like the role (and trust relationship) is created, but not the actual pod identity association with a service account. Considering this commit removed Karpenter support in favour of using this module, I was surprised that the submodule for Karpenter does not create the pod identity association. From testing, it doesn't seem like the namespace or service account in the association needs to exist.Worth mentioning I'm happy to create a PR to add this, but wanted to check if there was a reason it wasn't included. Thanks!
The text was updated successfully, but these errors were encountered: