kong ingress controller need support for multiple ports per service

[zhigang]

Summary

Kong Ingress controller "0.5.0" not support for multiple ports per service.

Kong Ingress controller version
0.5.0

Kong version
1.2

Kubernetes version

Kubernetes Cluster version v1.10 (v1.10.12) - git (clean) commit c757b93cf034d49af3a3b8ecee3b9639a7a11df7 - platform linux/amd64

What happened

This is my ingress yaml , there have two ports need setting.

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  annotations:
    configuration.konghq.com: need-strip-path
    kubernetes.io/ingress.class: kong
  labels:
    app: test-api
  name: test-api
  namespace: staging
spec:
  rules:
  - host: test.mydomain.com
    http:
      paths:
      - backend:
          serviceName: test-api
          servicePort: 5000
        path: /test-api
      - backend:
          serviceName: test-api
          servicePort: 5001
        path: /test-socket

kong ingress controller error:

E0722 12:39:24.220304       1 controller.go:125] unexpected failure updating Kong configuration:
error creating a valid state for Kong: duplicate upstream definitions found for: 'test-api.staging.svc'
W0722 12:39:24.220345       1 queue.go:113] requeuing staging/test-api, err error creating a valid state for Kong: duplicate upstream definitions found for: 'test-api.staging.svc'

[ismailbaskin]

I think the upstream name should contain port number too.

[provgregoryabdo]

This was working for me with the helm chart version 0.7.0. I have updated to 0.12.1 and now both ports are showing up in the target.

KongRDSDB=> select * from targets WHERE upstream_id = '214fd01a-4733-4dc4-bb06-123271a393d2';
                  id                  |         created_at         |             upstream_id              |       target       | weight | tags 
--------------------------------------+----------------------------+--------------------------------------+--------------------+--------+------
 5df98361-eb76-4ca0-b636-315969865f5f | 2019-08-13 21:24:45.16+00  | 214fd01a-4733-4dc4-bb06-123271a393d2 | 100.120.0.61:10020 |    100 | 
 6f6e09d0-4560-4a66-b7b4-bf56dc30ab3f | 2019-08-13 21:24:44.931+00 | 214fd01a-4733-4dc4-bb06-123271a393d2 | 100.120.0.61:8025  |    100 | 
(2 rows)

This obviously is causing issues, things supposed to got port 10020 are going to both 10020 and 8025 and things supposed to goto 8025 are going to both as well.

[provgregoryabdo]

Thanks so much @rainest ! Really looking forward to this feature.