Replies: 2 comments 1 reply
-
Hey @leynebe, it seems you are missing out the protocol on the repository URL. Please try to add the repository using a full-qualified URL, starting with |
Beta Was this translation helpful? Give feedback.
-
I think you will need to add the Helm repository explicitly to the Argo CD configuration and enable OCI support for it. Since this feature is not (yet) exposed in the web UI, you will have to do it using the CLI's argocd repo add --type helm --name <repo-name> --enable-oci <your-repository-url> If you get authentication failure, try to pass |
Beta Was this translation helpful? Give feedback.
-
Hi all
I'm pretty new to Argo so I might have missed something, but I'm stumbling upon something that I don't think is implemented yet.
AWS recently added support to push Helm charts to ECR. (https://docs.aws.amazon.com/AmazonECR/latest/userguide/push-oci-artifact.html) The first step in it is to enable the helm experimental option, this shows me this helm OCI stuff is pretty new. (https://helm.sh/docs/topics/registries/)
We pushed a generic helm chart to ECR to be used by multiple applications deployed to K8S using ArgoCD.
To accomplish this we wanted to add AWS ECR as a repository source in ArgoCD, that's where errors occurred.
I also wasn't able to add the ECR as a repository in the UI, but I was able to add it via the CLI. I cannot test if it works though.
There is an additional issue in that "aws ecr get-login-password" only provides the password for 12 hrs. (Which is probably not a problem you should/can solve.)
We're looking at just putting the chart in a git repo and be done with it instead of using AWS ECR.
Thanks for any helmful feedback :)
Ben
Beta Was this translation helpful? Give feedback.
All reactions