title: Helm install or upgrade release failed on Kubernetes cluster: the server could not find the requested resource or UPGRADE FAILED: no deployed releases
body: <p>Using helm for deploying chart on my Kubernetes cluster, since one day, I can't deploy a new one or upgrading one existed.</p>
  
  <p>Indeed, each time I am using helm I have an error message telling me that it is not possible to install or upgrade ressources.</p>
  
  <p>If I run <code>helm install --name foo . -f values.yaml --namespace foo-namespace</code> I have this output:</p>
  
  <blockquote>
    <p>Error: release foo failed: the server could not find the requested
    resource</p>
  </blockquote>
  
  <p>If I run <code>helm upgrade --install foo . -f values.yaml --namespace foo-namespace</code> or <code>helm upgrade foo . -f values.yaml --namespace foo-namespace</code> I have this error:</p>
  
  <blockquote>
    <p>Error: UPGRADE FAILED: "foo" has no deployed releases</p>
  </blockquote>
  
  <p>I don't really understand why.</p>
  
  <p>This is my helm version:</p>
  
  <pre><code>Client: &amp;version.Version{SemVer:"v2.12.3", GitCommit:"eecf22f77df5f65c823aacd2dbd30ae6c65f186e", GitTreeState:"clean"}
  Server: &amp;version.Version{SemVer:"v2.12.3", GitCommit:"eecf22f77df5f65c823aacd2dbd30ae6c65f186e", GitTreeState:"clean"}
  </code></pre>
  
  <p>On my kubernetes cluster I have tiller deployed with the same version, when I run <code>kubectl describe pods tiller-deploy-84b... -n kube-system</code>:</p>
  
  <pre><code>Name:               tiller-deploy-84b8...
  Namespace:          kube-system
  Priority:           0
  PriorityClassName:  &lt;none&gt;
  Node:               k8s-worker-1/167.114.249.216
  Start Time:         Tue, 26 Feb 2019 10:50:21 +0100
  Labels:             app=helm
                      name=tiller
                      pod-template-hash=84b...
  Annotations:        &lt;none&gt;
  Status:             Running
  IP:                 &lt;IP_NUMBER&gt;
  Controlled By:      ReplicaSet/tiller-deploy-84b8...
  Containers:
    tiller:
      Container ID:   docker://0302f9957d5d83db22...
      Image:          gcr.io/kubernetes-helm/tiller:v2.12.3
      Image ID:       docker-pullable://gcr.io/kubernetes-helm/tiller@sha256:cab750b402d24d...
      Ports:          44134/TCP, 44135/TCP
      Host Ports:     0/TCP, 0/TCP
      State:          Running
        Started:      Tue, 26 Feb 2019 10:50:28 +0100
      Ready:          True
      Restart Count:  0
      Liveness:       http-get http://:44135/liveness delay=1s timeout=1s period=10s #success=1 #failure=3
      Readiness:      http-get http://:44135/readiness delay=1s timeout=1s period=10s #success=1 #failure=3
      Environment:
        TILLER_NAMESPACE:    kube-system
        TILLER_HISTORY_MAX:  0
      Mounts:
        /var/run/secrets/kubernetes.io/serviceaccount from helm-token-... (ro)
  Conditions:
    Type              Status
    Initialized       True 
    Ready             True 
    ContainersReady   True 
    PodScheduled      True 
  Volumes:
    helm-token-...:
      Type:        Secret (a volume populated by a Secret)
      SecretName:  helm-token-...
      Optional:    false
  QoS Class:       BestEffort
  Node-Selectors:  &lt;none&gt;
  Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                   node.kubernetes.io/unreachable:NoExecute for 300s
  Events:
    Type    Reason     Age   From                   Message
    ----    ------     ----  ----                   -------
    Normal  Scheduled  26m   default-scheduler      Successfully assigned kube-system/tiller-deploy-84b86cbc59-kxjqv to worker-1
    Normal  Pulling    26m   kubelet, k8s-worker-1  pulling image "gcr.io/kubernetes-helm/tiller:v2.12.3"
    Normal  Pulled     26m   kubelet, k8s-worker-1  Successfully pulled image "gcr.io/kubernetes-helm/tiller:v2.12.3"
    Normal  Created    26m   kubelet, k8s-worker-1  Created container
    Normal  Started    26m   kubelet, k8s-worker-1  Started container
  </code></pre>
  
  <p>Is someone have faced the same issue ?</p>
  
  <hr>
  
  <p>Update:</p>
  
  <p>This the folder structure of my actual chart named foo:
  structure folder of the chart:</p>
  
  <pre><code>&gt; templates/
    &gt; deployment.yaml 
    &gt; ingress.yaml
    &gt; service.yaml
  &gt; .helmignore
  &gt; Chart.yaml 
  &gt; values.yaml
  </code></pre>
  
  <p>I have already tried to delete the chart in failure using the delete command <code>helm del --purge foo</code> but the same errors occurred.</p>
  
  <p>Just to be more precise, the chart foo is in fact a custom chart using my own private registry. ImagePullSecret are normally setting up.</p>
  
  <p>I have run these two commands <code>helm upgrade foo . -f values.yaml --namespace foo-namespace --force</code> | <code>helm upgrade --install foo . -f values.yaml --namespace foo-namespace --force</code> and I still get an error:</p>
  
  <pre><code>UPGRADE FAILED
  ROLLING BACK
  Error: failed to create resource: the server could not find the requested resource
  Error: UPGRADE FAILED: failed to create resource: the server could not find the requested resource
  </code></pre>
  
  <p>Notice that foo-namespace already exist. So the error don't come from the namespace name or the namespace itself. Indeed, if I run <code>helm list</code>, I can see that the <strong>foo</strong> chart is in a <code>FAILED</code> status.</p>