helm: v3.12.0 Failed deployments
Output of helm version: version.BuildInfo{Version:“v3.12.0”, GitCommit:“c9f554d75773799f72ceef38c51210f1842a1dea”, GitTreeState:“clean”, GoVersion:“go1.20.3”}
Cloud Provider/Platform (AKS, GKE, Minikube etc.): EKS.
In our pipelines , we download the latest version of helm3 and use it for deployments. Starting with three hours ago, our deployments started failing with the following error.
Error: UPGRADE FAILED: error validating "": error validating data: the server responded with the status code 426 but did not return more information
I reverted to the last working version of helm in our pipelines ( v3.11.3 ) and our pipelines are working now.
curl -L https://git.io/get_helm.sh | bash -s -- --version v3.11.3
About this issue
- Original URL
- State: closed
- Created a year ago
- Reactions: 10
- Comments: 26 (10 by maintainers)
Commits related to this issue
- ci(gitlab): Allow failures when deploying the review app Links: - https://gitlab.com/opensavvy/formulaide/-/issues/297 - https://github.com/helm/helm/issues/12071 — committed to CLOVIS-AI/Formulaide by CLOVIS-AI a year ago
- Upgrade Helm from version 3.12.0 to 3.12.2. As this is a non-breaking change in the Helm CLI, the Garden helm provider should function seamlessly. Refer to the Helm 3.12.2 release for more details: h... — committed to numb95/garden by numb95 7 months ago
- Upgrade Helm from version 3.12.0 to 3.12.2. As this is a non-breaking change in the Helm CLI, the Garden helm provider should function seamlessly. Refer to the Helm 3.12.2 release for more details: h... — committed to garden-io/garden by numb95 7 months ago
- improvement(helm): update helm to `3.12.2` Upgrade Helm from version 3.12.0 to 3.12.2. As this is a non-breaking change in the Helm CLI, the Garden helm provider should function seamlessly. Refer to... — committed to garden-io/garden by numb95 7 months ago
- improvement(helm): update helm to `3.12.2` Upgrade Helm from version 3.12.0 to 3.12.2. As this is a non-breaking change in the Helm CLI, the Garden helm provider should function seamlessly. Refer to... — committed to garden-io/garden by numb95 7 months ago
- improvement(helm): update helm to `3.12.2` (#5497) Upgrade Helm from version 3.12.0 to 3.12.2. As this is a non-breaking change in the Helm CLI, the Garden helm provider should function seamlessly. ... — committed to garden-io/garden by vvagaytsev 7 months ago
I have the same issue, It doesn’t seem to have anything to do with any helm repo. I’m using it to deploy a local (on-disk) helm chart. Seems to have something to do with the connection to the cluster.
EDIT I fixed it by downgrading to previous helm version.
For other people, like me that is using Gitlab CI.
Note: make sure bash and openssl is installed first.
Kubernetes patch release scheduled for 2023-05-17
@joejulian added debug variable to my CI and upgraded to 3.12 again. Debug log is huge, and i am not really into go, but this looks intresting to me:
In particular this one:
As said, there is KAS running in my case: https://docs.gitlab.com/ee/administration/clusters/kas.html
Throwing the same command directly against my cluster works fine.
I had the issue with 3.12.0, it seems to work fine with 3.12.1
@joejulian #12096 does the job for me.
I’ve used it both 1.24 and 1.25, same issue on both.