-
Notifications
You must be signed in to change notification settings - Fork 122
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
Request for aws_eks_pod_identity_association
resource
#985
Comments
This has been released now Terraform side. |
Hello, just wondering how can we help get this added to this provider. Actually, I don't know what the process anyway to follow the Terraform's recent changes. Could you please guide us? |
Hello, is there anyone working on this? |
Yes. There are a couple open PRs where I see the core maintainers testing various examples with the new terraform provider version. Terraform provider AWS version 5.x contains breaking changes, and many resources have been migrated from the terraform plugin SDK to the terraform plugin framework, which is not yet supported by the new no-fork upjet architecture that brought huge performance improvements. That's being worked on, too. If you want to be more up to date with what's happening with this project, check out the crossplane community meeting every 2 weeks. The notes are public, past meetings are on YouTube, and anyone can join the zoom. More details are on crossplane slack. |
Thanks a lot @mbbush , I'll follow-up with meetings. Cheers! |
What resource do you need?
Terraform Resource Name: aws_eks_pod_identity_association
What is your use case?
It's significantly less painful than using IRSA with EKS and it's currently brewing over at the terraform provider.
https://aws.amazon.com/blogs/aws/amazon-eks-pod-identity-simplifies-iam-permissions-for-applications-on-amazon-eks-clusters/
Putting this issue up to get ahead of that and track the issue.
The text was updated successfully, but these errors were encountered: