We created a new EKS cluster, set up this Github actions in our pipeline.
It was able to assume our EKS role. When it ran the helm upgrade command, we got this error below
Error: UPGRADE FAILED: "release-name" has no deployed releases
It seems like because there is no releases, it fails. I forked the repo and added a --force flag to the shell script and it was able to bypass that error and launch our helm chart.
On subsequent runs, it seems to be fine.
Any thoughts?
I'd ideally like to delete my fork/action and use this (I can submit a PR but would like to know what the best possible option here is).
- Could include a
force option in the with list and pass that flag if that is set
- google/stackoverflow/GH issues recommends running
helm uninstall <release_name> or helm delete <release_name> before running the upgrade command as a possible solution (however running these locally didnt seem to have any affect/builds kept failing until I added the --force option)
We created a new EKS cluster, set up this Github actions in our pipeline.
It was able to assume our EKS role. When it ran the
helm upgradecommand, we got this error belowError: UPGRADE FAILED: "release-name" has no deployed releasesIt seems like because there is no releases, it fails. I forked the repo and added a
--forceflag to the shell script and it was able to bypass that error and launch our helm chart.On subsequent runs, it seems to be fine.
Any thoughts?
I'd ideally like to delete my fork/action and use this (I can submit a PR but would like to know what the best possible option here is).
forceoption in the with list and pass that flag if that is sethelm uninstall <release_name>orhelm delete <release_name>before running the upgrade command as a possible solution (however running these locally didnt seem to have any affect/builds kept failing until I added the --force option)