Replies: 3 comments
-
Did you end up solving this? Same issue. ArgoCD and GCP, but same thing. |
Beta Was this translation helpful? Give feedback.
0 replies
-
What if you just remove auth: {} from ECRAuthorizationToken, it should use the external-secret controller's authentication?
|
Beta Was this translation helpful? Give feedback.
0 replies
-
Think we solved it just by adding ECR access to the argocd-server SA and putting it all in the argocd namespace.
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
Go is not my strong point, however ECRAuthorizationToken does not appear to be able to read a service account in another namespace. Is this by design or a bug ?
This results in the following errors
It appears to try and read the serviceAccountRef from the argocd namespace, not the defined external-secrets namespace.
Beta Was this translation helpful? Give feedback.
All reactions