Open efbicief opened 11 months ago
Is there a work around for this?
It seems to work if you put the full repository URL under repository:
, eg:
dependencies:
- name: some-chart-name
version: 1.2.3
repository: oci://some-oci-repo.com
And if the chart is not at the root of the repo (eg. if charts are indexed by publisher), you can do:
dependencies:
- name: some-chart-name
version: 1.2.3
repository: oci://some-oci-repo.com/some/path/in/repo
ArgoCD versions 2.10 and below have reached EOL. Can you upgrade and let us know if the issue is still present, please?
Checklist:
argocd version
.Describe the bug
I have an application which deploys a Helm chart defined in git. This chart has a dependency which needs to be pulled from an OCI Helm repository, which I have configured with a repository secret. Syncing the application fails with:
Failed to load target state: failed to generate manifest for source 1 of 1: rpc error: code = Unknown desc = Manifest generation error (cached): 'helm repo add helm-oci-repo' failed exit status 1: Error: could not find protocol handler for:
To Reproduce
Define repository
In ArgoCD I can see that it can successfully connect to the repo.
Define helm chart
Chart.yaml
:dependencies:
name: my-dependency-chart version: 1.2.3 repository: "@helm-oci-repo"
Deploy with applicationset with:
We see a sync error in argocd:
Failed to load target state: failed to generate manifest for source 1 of 1: rpc error: code = Unknown desc = Manifest generation error (cached):
helm repo add docker-virtualfailed exit status 1: Error: could not find protocol handler for:
OCI repos are not supported by
helm repo add
, but Argo CD tries to add them.Expected behavior ArgoCD should not attempt to
helm repo add
any repos withenableOCI: "true"
set, instead it should just try to pull using the url (prepended withoci://
)Version
Logs