<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>Kubernetes 1.16 <a href="https://v1-16.docs.kubernetes.io/docs/setup/release/#deprecations-and-removals" rel="nofollow noreferrer">removed the &quot;beta&quot; versions of several resources in favor of stable versions</a>.  Kubernetes only <a href="https://kubernetes.io/docs/setup/release/version-skew-policy/" rel="nofollow noreferrer">supports the three most recent releases</a>, and as I'm writing this 1.19 is the current version, so no current supported version of Kubernetes (1.17, 1.18, or 1.19) supports <code>apiVersion: apps/v1beta2</code> at all.</p>
<p>You need to find the specific StatefulSet declaration in your Helm chart and change its version to <code>apiVersion: apps/v1</code>.  This may work without further changes; if not, you'll probably get a validation error when you try to install the release.  You will likely hit similar issues with Deployments.</p>
<p>This is not related to the (Helm v2) Tiller process, and you should not try to work around this by making changes to the cluster configuration.  I've found Helm v2 to be a little finicky around some kinds of changes and you may need to <code>helm del --purge</code> your existing installation before attempting a redeploy.</p>
