helm: Tiller issue after upgrading : the server could not find the requested resource
Hi, our gitlab-runner updated to latest version, so we updated helm/tiller at k8s but then all deploys of our charts failed with :
[tiller] 2018/09/26 13:38:51 warning: Upgrade "some-helm-release " failed: the server could not find the requested resource
I can’t find what’s the resource failing. We checked our k8s cluster and everything’s working ok. Actually, we manually deployed some charts with no issue. We can’t perform helm upgrades of deployed releases.
Edit: Works without --wait (which we need in prod)
Any thoughts?
Thanks!
Output of helm version:
Client: &version.Version{SemVer:“v2.11.0”, GitCommit:“2e55dbe1fdb5fdb96b75ff144a339489417b146b”, GitTreeState:“clean”}
Server: &version.Version{SemVer:“v2.11.0”, GitCommit:“2e55dbe1fdb5fdb96b75ff144a339489417b146b”, GitTreeState:“clean”}
Output of kubectl version:
Client Version: version.Info{Major:“1”, Minor:“8”, GitVersion:“v1.8.4”, GitCommit:“9befc2b8928a9426501d3bf62f72849d5cbcd5a3”, GitTreeState:“clean”, BuildDate:“2017-11-20T05:28:34Z”, GoVersion:“go1.8.3”, Compiler:“gc”, Platform:“linux/amd64”}
Server Version: version.Info{Major:“1”, Minor:“8”, GitVersion:“v1.8.4”, GitCommit:“9befc2b8928a9426501d3bf62f72849d5cbcd5a3”, GitTreeState:“clean”, BuildDate:“2017-11-20T05:17:43Z”, GoVersion:“go1.8.3”, Compiler:“gc”, Platform:“linux/amd64”}
Cloud Provider/Platform (AKS, GKE, Minikube etc.):
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 5
- Comments: 23 (7 by maintainers)
This commit broke it efadbd88035654b2951f3958167afed014c46bc6
This finds a deployment with “extensions/v1beta1” and then calls the api with “apps/v1” which results in “the server could not find the requested resource”
Maybe @adamreese can have a look at it
Was just running into this issue, I:
helm install --dry-run --debug ...kubectl create -f ...… and found there was a syntax error in a a PVC definition in my chart. Something to try if this issue is a complete blocker.
Same issue after upgrading to 2.11.0 version.
5 months and a minor release later, is this ever going to get fixed?
We also had the issue of the mysterious
failed: the server could not find the requested resourcebecause of a typo in a service account manifest. we hadaapiVersion: v1instead ofapiVersion: v1and strangely this typo worked on the previous helm release.Same issue here with Helm v2.11.0 - seems
--waitis broken in this release (2.9.1 and 2.10.0 work)