Summary
The multi-ALB support allows us to reference multiple ingresses and it was requested here - #2471. The problem with the solution is that only one servicePort can be specified. Interestingly, the author of this comment - #710 (comment) - suggested a more generic way for traffic routing, but it wasn't implemented this way.
Use Cases
We've got a single web-application application that handles incoming traffic on two ports, say 8080, 8081. A single Service object handles both ports:
spec: ports: - port: 8080 ... - port: 8081 ...
Two Ingresses (AWS ALB) routes the traffic to target groups with different ports, say Ingress A -> 8080, Ingress B -> 8081
With the current options, we can't use ALB traffic routing. Please assist.
Message from the maintainers:
Need this enhancement? Give it a 👍. We prioritize the issues with the most 👍.
Summary
The multi-ALB support allows us to reference multiple ingresses and it was requested here - #2471. The problem with the solution is that only one servicePort can be specified. Interestingly, the author of this comment - #710 (comment) - suggested a more generic way for traffic routing, but it wasn't implemented this way.
Use Cases
We've got a single web-application application that handles incoming traffic on two ports, say 8080, 8081. A single Service object handles both ports:
spec: ports: - port: 8080 ... - port: 8081 ...Two Ingresses (AWS ALB) routes the traffic to target groups with different ports, say Ingress A -> 8080, Ingress B -> 8081
With the current options, we can't use ALB traffic routing. Please assist.
Message from the maintainers:
Need this enhancement? Give it a 👍. We prioritize the issues with the most 👍.