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
[ x ] I've searched the issue queue to verify this is not a duplicate bug report.
[ x ] I've included steps to reproduce the bug.
[ x ] I've pasted the output of kargo version.
[ x ] I've pasted logs, if applicable.
Description
When using a helm chart in a private repo as an umbrella chart dependency, the provided credentials, which are used by the warehouse, are not used during the promotion.
Screenshots
N/A
Steps to Reproduce
Below is my setup with the private registry and repo names changed. I have secrets in place to access both the private GitHub repo and the private Helm chart repo. The warehouse can access both without issue and generate freight when values change. However, promotions fail as Helm is unable to access the private Helm repo.
╰─$ kargo version
Client Version: v0.5.2
Server Version: v0.6.0```
# Logs
kargo-controller-7d69c8cb9-2wsfv controller time="2024-05-09T15:54:30Z" level=error msg="error executing Promotion: error executing Git-based promotion mechanisms: error executing Helm promotion mechanism: error updating dependencies for chart "apps/infra/goldilocks/stg": :error running helm dependency update for chart at "/tmp/repo-3645567429/repo/apps/infra/goldilocks/stg": error executing cmd [/usr/local/bin/helm dependency update /tmp/repo-3645567429/repo/apps/infra/goldilocks/stg]: Getting updates for unmanaged Helm repositories...\n...Unable to get an update from the "https://ourprivaterepo.jfrog.io/artifactory/api/helm/fc-helm\" chart repository:\n\tfailed to fetch https://ourprivaterepo.jfrog.io/artifactory/api/helm/fc-helm/index.yaml : 401 \n...Successfully got an update from the "https://charts.fairwinds.com/stable\" chart repository\nError: no cached repository for helm-manager-11bf74fc0d880338f4cda581406d0ee8f0b023a55b172c0da9c0fc9fef9c7d76 found. (try 'helm repo update'): open /tmp/.cache/helm/repository/helm-manager-11bf74fc0d880338f4cda581406d0ee8f0b023a55b172c0da9c0fc9fef9c7d76-index.yaml: no such file or directory\n" freight=53e2793ed8502e48dacd3f2d934852d498896fb8 namespace=kargo-goldilocks promotion=stg.01hxf1085akg8yc3rb76wqxqte.53e2793 stage=stg
The text was updated successfully, but these errors were encountered:
Checklist
kargo version
.Description
When using a helm chart in a private repo as an umbrella chart dependency, the provided credentials, which are used by the warehouse, are not used during the promotion.
Screenshots
N/A
Steps to Reproduce
Below is my setup with the private registry and repo names changed. I have secrets in place to access both the private GitHub repo and the private Helm chart repo. The warehouse can access both without issue and generate freight when values change. However, promotions fail as Helm is unable to access the private Helm repo.
Version
kargo-controller-7d69c8cb9-2wsfv controller time="2024-05-09T15:54:30Z" level=error msg="error executing Promotion: error executing Git-based promotion mechanisms: error executing Helm promotion mechanism: error updating dependencies for chart "apps/infra/goldilocks/stg": :error running
helm dependency update
for chart at "/tmp/repo-3645567429/repo/apps/infra/goldilocks/stg": error executing cmd [/usr/local/bin/helm dependency update /tmp/repo-3645567429/repo/apps/infra/goldilocks/stg]: Getting updates for unmanaged Helm repositories...\n...Unable to get an update from the "https://ourprivaterepo.jfrog.io/artifactory/api/helm/fc-helm\" chart repository:\n\tfailed to fetch https://ourprivaterepo.jfrog.io/artifactory/api/helm/fc-helm/index.yaml : 401 \n...Successfully got an update from the "https://charts.fairwinds.com/stable\" chart repository\nError: no cached repository for helm-manager-11bf74fc0d880338f4cda581406d0ee8f0b023a55b172c0da9c0fc9fef9c7d76 found. (try 'helm repo update'): open /tmp/.cache/helm/repository/helm-manager-11bf74fc0d880338f4cda581406d0ee8f0b023a55b172c0da9c0fc9fef9c7d76-index.yaml: no such file or directory\n" freight=53e2793ed8502e48dacd3f2d934852d498896fb8 namespace=kargo-goldilocks promotion=stg.01hxf1085akg8yc3rb76wqxqte.53e2793 stage=stgThe text was updated successfully, but these errors were encountered: