<p>Using different tools (kubent for example) I see that I have deprecated API in my cluster. For example</p>
<pre><code>Type: Ingress Name: kibana  API: networking.k8s.io/v1beta1
</code></pre>
<p>But when I open Ingress itself, I can see this:</p>
<pre><code>apiVersion: networking.k8s.io/v1
kind: Ingress
  managedFields:
    - manager: Go-http-client
      operation: Update
      apiVersion: networking.k8s.io/v1beta1
</code></pre>
<p>So, it shows that API of my Ingress is actually &quot;v1&quot;, not &quot;beta&quot;. But &quot;managedFields&quot; section indeed has &quot;v1beta1&quot; API. According to official <a href="https://kubernetes.io/docs/reference/using-api/server-side-apply/" rel="nofollow noreferrer">documentation</a>, this is server side API that should not be edited by user.</p>
<p>So, my question is - should/can I do anything with deprecated API in this &quot;managedField&quot;? Will there be any issues during upgrade to next k8s version? Because currently my GCP console shows that there will be problems.</p>

<p>There will be no issue while upgrading your Kubernetes cluster to the latest version even if you have deprecated API version in the <code>managed field</code> in the ingress configuration.  The reason why you still see versions <strong>“/v1beta1”</strong> in the UI is because there are different parts of GKE that rely on both versions(v1 and v1beta1).</p>
<p>Between the two Kubernetes versions 1.19 and 1.21, both endpoints <code>networking.k8s.io/v1</code> and <code>extensions/v1beta1</code> are supported. They are functionally identical, and it is down to the given UI's preference for which version is displayed. So it won’t affect the functionality of your Ingress. As said, GKE clusters were created on <a href="https://cloud.google.com/kubernetes-engine/docs/deprecations/apis-1-22#ingress-v122" rel="nofollow noreferrer">versions 1.22</a> and later stopped supporting extensions/v1beta1 and networking.k8s.io/v1beta1 Ingress.</p>
