You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I am trying to use the new OCI support in Argo CD 3.1 to create an application with a source that is an AWS ECR repository, but my application fails to sync with an error:
message: 'Failed to load target state: failed to generate manifest for source
1 of 1: rpc error: code = Unknown desc = failed to resolve revision "0.0.2":
cannot get digest for revision 0.0.2: HEAD "https://1234567890.dkr.ecr.eu-west-1.amazonaws.com/v2/cluster-deployment/core-eks-cluster-dev01/test-oci/manifests/0.0.2":
basic credential not found'
I am using External-secrets operator to manage the AWS ECR auth token (having given the argocd-repo-server serviceaccount an IRSA annotation linked to a IAM role with permissions to get the token):
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, I am trying to use the new OCI support in Argo CD 3.1 to create an application with a source that is an AWS ECR repository, but my application fails to sync with an error:
My guess is that there is a mismatch between my repository setup and the
repoURL
in my application resource, and they are not matching. Unfortunately the new example in the docs https://argo-cd.readthedocs.io/en/latest/user-guide/oci/ does not give an example of how to set up the repository. I rummaged in the MR raised by @blakepettersson and saw that a new type was created (https://github.com/argoproj/argo-cd/pull/18646/files#diff-667adf2824d085efeff7ce304e59e98060281c2741bf39755db16ccfebe66bd5R72), so I copied that and the syntax of the other fields too, but I wonder if something else is missing from my repository secret? Or perhaps the AWS credentials I have put in the password are incorrect?Here is my config:
version: 3.1.1
Application
I am using External-secrets operator to manage the AWS ECR auth token (having given the argocd-repo-server serviceaccount an IRSA annotation linked to a IAM role with permissions to get the token):
This sets up the secret successfully:
Where the opaque values are:
digieco-eks-components-repo-ecr-localaccount
eyJwYXlsb2FkIjoiWn....
oci
oci://1234567890.dkr.ecr.eu-west-1.amazonaws.com
AWS
I have tried:
oci://1234567890.dkr.ecr.eu-west-1.amazonaws.com/*
oci://1234567890.dkr.ecr.eu-west-1.amazonaws.com/**
as well, with no luck.
Any insight into this error would be greatly appreciated.
Thanks,
Mark
Beta Was this translation helpful? Give feedback.
All reactions