-
Notifications
You must be signed in to change notification settings - Fork 180
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
Action does not support EKS pod identities #624
Comments
Current Workaround
|
Another workaround that might be better if you are using kubernetes driver for buildx is to not use If you are using Pod Identity with EKS this is needed to get buildx with k8s pushing to private ECR. Maybe this saves someone time.
|
Describe the bug
We are migrating workloads to EKS - in particular Github Actions runners. The runner scalesets run as service accounts wired up to AWS EKS Pod Identities. We run v2 of the action and receive the following error:
To Reproduce
Create a test action that uses
amazon-ecr-login
in a pod/runner running in EKS and a service account identity.Expected behavior
The action discovers the creds mounted in the metadata path and uses them to authenticate with ECR.
Screenshots
No screenshots but we confirmed that raw
aws sts
commands are returning the correct assumed role that we'd expect.Desktop (please complete the following information):
EKS 1.29
Running 0.9.0 version of github action runner container and helm chart.
The text was updated successfully, but these errors were encountered: