-
Notifications
You must be signed in to change notification settings - Fork 174
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
[QUESTION] Credentials priority #419
Comments
I'm having a similar issue on self managed runners, I'd love to know the answer to this question. |
Could you paste the exact error from your logs here, covering any sensitive information? |
There is no error for ecr-login step, because kubernetes node has default IAM role attached with read permissions to ECR.
|
What OS is your runner? |
Amazon linux 2 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have EKS cluster in prod account (within AWS Organization). It has OIDC enabled and I manage permissions for pods through OIDC.
Configured custom runner on this cluster (with no role attached -> assume that it will get node default).
ECR is in another account.
Configured IAM identity provider for GitHub.
Pipeline should build docker image and push to ECR using kaniko.
On custom-runner it fails with unauthorised, on default
ubuntu-latest
from GitHub it works fine.Is it an issue or something is not configured properly?
Thanks
The text was updated successfully, but these errors were encountered: