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 still not working #4353
Comments
any news on this? I have the same issue and wonder why is this happen |
Hey @laiminhtrung1997 how are you man? So I have been testing and basically if you have a container registry you can change the NewSession function at provider/aws/session.go and remove the config variable from the session.NewSessionWithOptions props, like this. session, err := session.NewSessionWithOptions(session.Options{
SharedConfigState: session.SharedConfigEnable,
}) By doing that, you can use make build.push IMAGE=your-registry/external-dns To upload the image to you container image registry. I will be creating a PR to discuss what can be done and evaluate if the Config is really and how to extend it. Hope it helps you |
Dear @AleCo3lho |
Hey man, I am not sure if I understand the problem you are having, for me looks like you are using IRSA right? |
Dear @AleCo3lho When I start the Pod with the ServiceAccount that is associated with the IAM Role, the Pod does not have the volume eks-pod-identity-token. It does when I restart the Pod. |
What happened:
External DNS pod can't retrieve credentials
What you expected to happen:
External DNS to retrieve the credentials
How to reproduce it (as minimally and precisely as possible):
Run External DNS with pod identity in eks
Anything else we need to know?:
Environment:
external-dns --version
):The text was updated successfully, but these errors were encountered: