<p>After upgrading the Kubernetes version, I get the error:
<code>Error: failed decoding rader into objects: unable to recognize &quot;&quot;: no matches for kind &quot;StatefulSet&quot; in version &quot;apps/v1beta2&quot;</code>
After I did some research in StackOverflow and more similar issues on the net I found two ways to overcome:
Downgrade Kubernetes version - this solution is out of the question for now.
adding the following line to <code>--runtime-config=apps/v1beta1=true,apps/v1beta2=true,extensions/v1beta1/daemonsets=true,extensions/v1beta1/deployments=true,extensions/v1beta1/replicasets=true,extensions/v1beta1/networkpolicies=true,extensions/v1beta1/podsecuritypolicies=true </code> to <code> /etc/kubernetes/manifest/kube-apiserver.yaml</code> file.</p>
<p>I understood that this file located inside the docker image of the api-server itself, so I looked for this specific image but I found 3 images named
<code> kube-apiserver-ip-xx.xx.xx.xxx.eu-west-1.compute.internal</code> and the file <code>kube-apiserver.yaml</code> missing for all 3 of them.</p>
<p>So I continued with my research and find out that the file actually located inside the master and not in the pods.</p>
<p>In addition to the above, the build process is also using tiller which I cannot know if it's related to this issue and maybe even required some additional adaptions on the tiller config.
I read in some posts that I need to change the master node but I don't understand how can I find this specific node using kubectl.
So in summary I have two questions:</p>
<p>1.whether the tiller may effect the process of my desired solution?</p>
<p>2.where can I find the master node of the api-server and how can i get the access to it (i.e. which kubectl commands etc.).</p>
<p>I still a beginner with Kubernetes, helm and tiller so apologies for my ignorance.
gratitude</p>

Kobi
<p>As you know API version might be different or updated based on the k8s cluster version. So far i have understood, you have a helm chart which was deployed earlier and after upgrading the k8s cluster, you are getting this API version mismatch while redeploying it.
you have not mentioned the k8s version you're running now after upgrading.
So to solve this issue, you have to find out the exact api version for statefulset.Which can be done by using the below command.</p>
<pre><code>kubectl api-resources |grep statefulsets
</code></pre>
<p>You will get output with columns and one of them are APIGROUP which will be <code>apps</code>.</p>
<p>Now try to get the api-versions from the below command.</p>
<pre><code>kubectl api-versions |grep apps
</code></pre>
<p>you will get the exact version which can be further verify using below command.</p>
<pre><code>kubectl explain statefulsets
</code></pre>
<p>the output will have the VERSION field which is the supported api version for statefulsets.</p>
<p>Now edit your helm chart's deployment.yml file and change <code>apiVersion </code> with the new api version  that you got from the command and redeploy.</p>
