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
Describe the bug
Hi there! I want to use secrets-store-csi-driver-provider-aws with ArgoCD and in order to create an application with the helm as a dependency, I need to provide a path to Chart. Currently, it is not available.
To Reproduce
Consider this Chart.yaml
If I run helm dependency update command, it will download an archive of current charts and create a Chart.lock file.
But I can't run the same command for this Chart.yaml:
I am getting the error: Error: secrets-store-csi-provider-aws chart not found in repo https://kubernetes-sigs.github.io/secrets-store-csi-driver/charts.
This link provided in the documentation lead to webpage, not to the chart:
Do you also notice this bug when using a different secrets store provider (Vault/Azure/GCP...)? No
Expected behavior Chart.lock and archive of charts downloaded.
Environment:
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered:
Have you tried following? I am installing with ArgoCD and it is working. repoURL: https://aws.github.io/secrets-store-csi-driver-provider-aws chart: secrets-store-csi-driver-provider-aws targetRevision: 0.3.4
Describe the bug
Hi there! I want to use
secrets-store-csi-driver-provider-aws
with ArgoCD and in order to create an application with the helm as a dependency, I need to provide a path to Chart. Currently, it is not available.To Reproduce
Consider this
Chart.yaml
If I run
helm dependency update
command, it will download an archive of current charts and create a Chart.lock file.But I can't run the same command for this
Chart.yaml
:I am getting the error:
Error: secrets-store-csi-provider-aws chart not found in repo https://kubernetes-sigs.github.io/secrets-store-csi-driver/charts
.This link provided in the documentation lead to webpage, not to the chart:
Do you also notice this bug when using a different secrets store provider (Vault/Azure/GCP...)?
No
Expected behavior
Chart.lock
and archive of charts downloaded.Environment:
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered: