-
Notifications
You must be signed in to change notification settings - Fork 19
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 plugin install failes on private runner #48
Comments
Thank you for your report. Does "private runner" mean self-hosted runner?
I'm not familiar with the |
This is true. But it would be great if the Action chrck if the plugin is present, than run helm plugin list or omit the download. |
Hello @jkroepke! I meet the same issue but I guess it's because of the network. I thought of two solutions
Did you use
and
|
Yes, it seems like an networking and a different issue compared to my one |
Its a bit tricky here, I not able to set this on a workflow level:
|
We faced the 404 Code
|
For unknown reasons, this actions uses an AWS EKS endpoint for fetching kubectl. Seems like AWS drop kubernetes 1.22 this works for me (using latest versions)
|
I have literary the same problem Error: The process '/bin/helm' failed with exit code 1 |
btw a workaround is to add something like the following to the top of your workflow.
The workflow can be fixed by changing those env variables to point to somewhere temp for the length of the run, not the global ones that helm uses by default. |
The official helmfile action solves the issue pretty well. |
There's an official one? This one comes up first when googling |
Oh nice. https://github.com/helmfile/helmfile-action looks like the real one |
I guess setting the env variable
HELM_DATA_HOME
to an tmp directory should fix this issue.The text was updated successfully, but these errors were encountered: