Description
What happened:
We have an ingress that uses this ExternalName service (to proxy to a non-k8s destination), and this worked with 1.11.4 and 1.20.0:
apiVersion: v1
kind: Service
metadata:
name: my-service
spec:
externalName: 10.20.30.40 # an ip address
type: ExternalName
As soon as we upgraded to 1.11.5 we started getting 503 errors from the ingress that points to this service.
What you expected to happen:
I looked through release notes and suspected it's related to #10989 and yes, doing the following fixed the issue:
apiVersion: v1
kind: Service
metadata:
name: my-service
spec:
externalName: server.hostname.example.com # a name that resolves to the IP address that we used previously
type: ExternalName
I am actually not 100% sure if using an IP address was legitimate to begin with, given the externalName field terminology - but it used to work, and now it does not. If you declare so, I will accept that we were "doing it wrong" and we can close this ticket so others can find it in case they run into this change.
NGINX Ingress controller version (exec into the pod and run /nginx-ingress-controller --version):
Upgrade 1.11.4 -> 1.11.5 and 1.20.0 -> 1.20.1
Kubernetes version (use kubectl version): v1.31.6
Environment: kOps 1.31.0
How was the ingress-nginx-controller installed: helm
How to reproduce this issue:
See above. I can provide any further details if necessary.
Anything else we need to know:
Thank you for maintaining this project, I suspect today was a stressful day!
Metadata
Metadata
Assignees
Labels
Type
Projects
Status