[v0.8-beta.1] Not finding backend pods

[tim-smart]

Here is my ingress and service: https://gist.github.com/tim-smart/5b6ff0de349e6cf1b8b73e625d7a208f

Working fine on v0.7.2.

Here is the generated backend block:

backend ariseconf19_ariseconf19_http
    mode http
    balance roundrobin
    acl https-request ssl_fc
    http-request set-header X-Original-Forwarded-For %[hdr(x-forwarded-for)] if { hdr(x-forwarded-for) -m found }
    http-request del-header x-forwarded-for
    option forwardfor
    http-response set-header Strict-Transport-Security "max-age=15768000"
    server srv001 127.0.0.1:1023 disabled weight 0 check inter 2s
    server srv002 127.0.0.1:1023 disabled weight 0 check inter 2s
    server srv003 127.0.0.1:1023 disabled weight 0 check inter 2s
    server srv004 127.0.0.1:1023 disabled weight 0 check inter 2s
    server srv005 127.0.0.1:1023 disabled weight 0 check inter 2s
    server srv006 127.0.0.1:1023 disabled weight 0 check inter 2s
    server srv007 127.0.0.1:1023 disabled weight 0 check inter 2s
    server srv008 127.0.0.1:1023 disabled weight 0 check inter 2s
    server srv009 127.0.0.1:1023 disabled weight 0 check inter 2s
    server srv010 127.0.0.1:1023 disabled weight 0 check inter 2s
    server srv011 127.0.0.1:1023 disabled weight 0 check inter 2s
    server srv012 127.0.0.1:1023 disabled weight 0 check inter 2s
    server srv013 127.0.0.1:1023 disabled weight 0 check inter 2s
    server srv014 127.0.0.1:1023 disabled weight 0 check inter 2s
    server srv015 127.0.0.1:1023 disabled weight 0 check inter 2s
    server srv016 127.0.0.1:1023 disabled weight 0 check inter 2s
    server srv017 127.0.0.1:1023 disabled weight 0 check inter 2s
    server srv018 127.0.0.1:1023 disabled weight 0 check inter 2s
    server srv019 127.0.0.1:1023 disabled weight 0 check inter 2s
    server srv020 127.0.0.1:1023 disabled weight 0 check inter 2s
    server srv021 127.0.0.1:1023 disabled weight 0 check inter 2s
    server srv022 127.0.0.1:1023 disabled weight 0 check inter 2s
    server srv023 127.0.0.1:1023 disabled weight 0 check inter 2s
    server srv024 127.0.0.1:1023 disabled weight 0 check inter 2s
    server srv025 127.0.0.1:1023 disabled weight 0 check inter 2s
    server srv026 127.0.0.1:1023 disabled weight 0 check inter 2s
    server srv027 127.0.0.1:1023 disabled weight 0 check inter 2s
    server srv028 127.0.0.1:1023 disabled weight 0 check inter 2s
    server srv029 127.0.0.1:1023 disabled weight 0 check inter 2s
    server srv030 127.0.0.1:1023 disabled weight 0 check inter 2s
    server srv031 127.0.0.1:1023 disabled weight 0 check inter 2s
    server srv032 127.0.0.1:1023 disabled weight 0 check inter 2s

v0.7.2 generates the following (on the same cluster):

backend ariseconf19-ariseconf19-80
    mode http
    balance roundrobin
    server 10.16.1.234:3000 10.16.1.234:3000 weight 1 check inter 2s
    server 10.16.4.83:3000 10.16.4.83:3000 weight 1 check inter 2s

[tim-smart]

Looks like issue was using a named targetPort on the service.

Any way around this without having to update all my service definitions?

[jcmoraisjr]

HI, thanks for reporting. No need to update your specs, the issue is in the controller side and should be fixed.

What the controller log say about this service?

[tim-smart]

Just a bunch of messages that look like:

No errors or anything unusual.

[jcmoraisjr]

Hi, v0.8-beta.2 is here and should fix this behavior. Please let me know if you still have any issue.