External IP set on NodePort ingress service is ignored,

[underyx]

NGINX Ingress controller version: 0.26.0 - 0.26.2 (working correctly on 0.25.1)

What happened: My ingress-nginx service is type: NodePort and lists externalIPs. After upgrading to 0.26, the ingress resources started being given the cluster-internal IP instead of the external IP of the service:

NAMESPACE   NAME                       HOSTS                       ADDRESS       PORTS     AGE
public      underyx-me-ingress         underyx.me,www.underyx.me   10.96.68.61   80, 443   7d18h

What you expected to happen: The ingress resources should report their external IP address.

How to reproduce it (as minimally and precisely as possible): Configure your service like this

apiVersion: v1
kind: Service
metadata:
  name: ingress-nginx
  namespace: ingress-nginx
  labels:
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/part-of: ingress-nginx
spec:
  type: NodePort
  ports:
    - name: http
      port: 80
      targetPort: 80
    - name: https
      port: 443
      targetPort: 443
  selector:
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/part-of: ingress-nginx
  externalIPs:
    - <add your external IP here>

Anything else we need to know: This was probably broken with #4490. It seems like #4700 attempted to fix it but it still doesn't work for me in 0.26.2.

[aledbf]

@underyx there is no release with #4700 (is planned for 0.27.0)

You can use quay.io/kubernetes-ingress-controller/nginx-ingress-controller:dev in the meantime.

[underyx]

Oh, I see, sorry then. I got confused by the tag marked on GitHub's UI on the commit page:

Does this not mean that the commit is part of the 0.26.2 release?

[aledbf]

Does this not mean that the commit is part of the 0.26.2 release?

Not sure why that got tagged in that release.

The release only contains one commit since 0.26.1 https://github.com/kubernetes/ingress-nginx/releases/tag/nginx-0.26.2