<p>Previously I was using the <code>extensions/v1beta1</code> api to create ALB on Amazon EKS. After upgrading the EKS to <code>v1.19</code> I started getting warnings:</p>
<pre><code>Warning: extensions/v1beta1 Ingress is deprecated in v1.14+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress
</code></pre>
<p>So I started to update my ingress configuration accordingly and deployed the ALB but the ALB is not launching in AWS and also not getting the ALB address.</p>
<p>Ingress configuration --&gt;</p>
<pre><code>apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: &quot;pub-dev-alb&quot;
  namespace: &quot;dev-env&quot;
  annotations:
    kubernetes.io/ingress.class: &quot;alb&quot;
    alb.ingress.kubernetes.io/scheme: internet-facing
    alb.ingress.kubernetes.io/target-type: ip

spec:
  rules:
  - host: &quot;dev.test.net&quot;
    http:
      paths:
      - pathType: Prefix
        path: &quot;/&quot;
        backend:
          service:
            name: &quot;dev-test-tg&quot;
            port:
              number: 80
</code></pre>
<p>Node port configuration --&gt;</p>
<pre><code>apiVersion: v1
kind: Service
metadata:
  name: &quot;dev-test-tg&quot;
  namespace: &quot;dev-env&quot;
spec:
  ports:
    - port: 80
      targetPort: 3001
      protocol: TCP
  type: NodePort
  selector:
    app: &quot;dev-test-server&quot;
</code></pre>
<p>Results ---&gt;</p>
<p><a href="https://i.stack.imgur.com/tc2rp.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/tc2rp.png" alt="enter image description here" /></a></p>
<p>Used <a href="https://aws.amazon.com/premiumsupport/knowledge-center/eks-alb-ingress-controller-setup/" rel="nofollow noreferrer">this documentation</a> to create ALB ingress controller.</p>
<p>Could anyone help me on here?</p>

<p>Your ingress should work fine even if you use newest Ingress. The warnings you see indicate that a new version of the API is available. You don't have to worry about it.</p>
<p>Here is the <a href="https://github.com/kubernetes/kubernetes/issues/94761" rel="nofollow noreferrer">explanation</a> why this warning occurs, even if you you use <code>apiVersion: networking.k8s.io/v1</code>:</p>
<blockquote>
<p>This is working as expected. When you create an ingress object, it can be read via any version (the server handles converting into the requested version).  <code>kubectl get ingress</code>  is an ambiguous request, since it does not indicate what version is desired to be read.</p>
<p>When an ambiguous request is made, kubectl searches the discovery docs returned by the server to find the first group/version that contains the specified resource.</p>
<p>For compatibility reasons,  <code>extensions/v1beta1</code>  has historically been preferred over all other api versions. Now that ingress is the only resource remaining in that group, and is deprecated and has a GA replacement, 1.20 will drop it in priority so that  <code>kubectl get ingress</code>  would read from  <code>networking.k8s.io/v1</code>, but a 1.19 server will still follow the historical priority.</p>
<p>If you want to read a specific version, you can qualify the get request (like  <code>kubectl get ingresses.v1.networking.k8s.io</code>  ...) or can pass in a manifest file to request the same version specified in the file (<code>kubectl get -f ing.yaml -o yaml</code>)</p>
</blockquote>
<p>You can also see a <a href="https://stackoverflow.com/questions/66080909">similar question</a>.</p>
