[nginx] Can't use named ports with ingress.kubernetes.io/service-upstream: "true"

[jordanjennings]

I am using the new annotation ingress.kubernetes.io/service-upstream: "true" and see that when I try to combine that with a named port in an ingress rule the ingress controller errors out with a message in the logs like:

Error: exit status 1
2017/10/02 19:50:03 [emerg] 58#58: invalid port in upstream "100.65.172.8:ui" in /tmp/nginx-cfg049697949:223
nginx: [emerg] invalid port in upstream "100.65.172.8:ui" in /tmp/nginx-cfg049697949:223
nginx: configuration file /tmp/nginx-cfg049697949 test failed

I'm using an ingress rule like this:

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: redis-ui
  annotations:
    ingress.kubernetes.io/force-ssl-redirect: "true"
    ingress.kubernetes.io/service-upstream: "true"
spec:
  rules:
  - host: my.domain.com
    http:
      paths:
      - path: /
        backend:
          serviceName: myapp
          servicePort: ui

This is with gcr.io/google_containers/nginx-ingress-controller:0.9.0-beta.13 and Kubernetes 1.7.3.

[aledbf]

ping @chrismoos

[chrismoos]

@jordanjennings I'll check this out, you might want to use the numerical port number in the ingress resource for now until it gets fixed.