-
Notifications
You must be signed in to change notification settings - Fork 808
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Helm repo index.yaml out of date #587
Comments
I'm facing the same issue also. I would like to install the newer version but I can't. I must say that the current published version has a bug that causes helm to always try to update it. The version on index.yaml is 0.4.0 but the published Chart's version is 0.3.0. |
PR created with the required update: #592 @leakingtapan could you please review it? |
@leakingtapan any return? I really need this feature because the current chart version that is available through the helm repo lacks a nodeAffinity rule that makes it not run inside fargate nodes. |
Hey @galindro I ended up forking this repo under my employer's organization (https://github.com/noteable-io/aws-ebs-csi-driver/tree/gh-pages) and manually publishing the latest version there it there; You should be able to do the same or you can use ours ( |
Yeah, I was considering it as well... |
This issue is the updated version of #557 |
The chart repo has been updated for the current releases |
@krmichel thank you |
Is your feature request related to a problem?/Why is this needed
The current Helm repo index.yaml (https://github.com/kubernetes-sigs/aws-ebs-csi-driver/blob/gh-pages/index.yaml) is out of date and pointing to an older version.
/feature
Describe the solution you'd like in detail
Please update the Helm repo index.yaml and point it to the published release of the 0.7.0 Helm chart
Describe alternatives you've considered
Current work around is to source the helm chart directly from the release as in the provided directions
Additional context
This would make the Helm chart experience consistent and up to date
The text was updated successfully, but these errors were encountered: