Open nan-coupa opened 2 years ago
Related to #7346 and comment: https://github.com/argoproj/argo-cd/issues/7436#issuecomment-1146480759
@nan-coupa Any updates about this issue? We ended up having the same problem in my team
@albertogdd, afaik still an issue since the PR is still failing after a rebase to the lastest commit. We ended up using ghcr as an OCI registry instead of trying to use the ArgoCD feature.
It isn't working still (image v2.7.9). Harbor supports native oci repository . It's important to support oci protocol inside ArgoCD.
Looks like this error message comes from Helm itself. Which is weird. We just call the helm
CLI. I'm not sure why this config is producing an error in Argo CD but (presumably) not Helm.
So it is clear for me.
In my chart oci repository address is running. good example:
dependencies:
- name: redis-commander
version: "0.3.0"
repository: "oci://registry.dev.company.pl/test-ba"
Oci repo alias has not supported by HELM ! Please read https://helm.sh/docs/topics/registries/
failed example:
dependencies:
- name: redis-commander
version: "0.3.0"
repository: "@oci-alias"
Checklist:
argocd version
.Describe the bug
ArgoCD does not support the combination of:
repository: "@name"
To Reproduce
See e2e PR example: https://github.com/argoproj/argo-cd/pull/9591/files
Helm Chart:
myrepo
is created per integration testse2e/fixtures/repos/repos.go
:Expected behavior
ArgoCD should support Helm chart
repository: @myrepo
syntax when said repository usesoci://
url.Screenshots
Version
This is the local running version:
Logs
PR #9591 e2e test error message same as local test results: https://github.com/argoproj/argo-cd/runs/6763941271?check_suite_focus=true#step:16:8347