-
Notifications
You must be signed in to change notification settings - Fork 13
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
Error when using EKS Pod Identity as credentials provider #103
Comments
it should work now that aws-sdk v2 has been upgraded. @vishal-chdhry is the latest untagged tag safe to use? we are still using the commit that corresponds to the v1 tag. |
@calvinbui yes you can use latest, it is safe to use |
thanks @vishal-chdhry the latest tag
i believe the problem is the aws-signer plugin's dependency is out of date based on the error message. the version of their website is |
@calvinbui I think you are right The signer binary was last updated in June 2023: Bin Download Page |
We've tried using EKS Pod Identity with kyervno-notation-aws (V1). It seems that the authentication endpoint is not taken into account by the application, so the role is not assumed. Using IRSA, it works correctly. In the same cluster, we have other containers that work perfectly with EKS Pod Identity.
Using IRSA :
Using Pod Identity association :
I can see the credentials varaibles set on the Pod :
The text was updated successfully, but these errors were encountered: