<p>I'm trying to find a solution for the problem that seems like something very common.</p>

<ol>
<li>I have a k8s cluster ip service which exposes two ports: 8088 and 60004</li>
<li>I would like to expose these same ports on ALB and not use path based routing</li>
</ol>

<p>This works for exposing one service on 8088 port:</p>

<pre><code>---
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: myingress
  namespace: myns
  annotations:
    kubernetes.io/ingress.class: alb
    alb.ingress.kubernetes.io/healthcheck-path: /ping
    alb.ingress.kubernetes.io/scheme: internet-facing
    alb.ingress.kubernetes.io/tags: Environment=dev,Team=test
    alb.ingress.kubernetes.io/target-type: ip
    alb.ingress.kubernetes.io/listen-ports: '[{"HTTP": 8088}]'
spec:
  rules:
    - host: myhost
      http:
        paths:
          - path: /*
            backend:
              serviceName: firstservice
              servicePort: 8088
</code></pre>

<p>How can the same thing be achieved for both services using ONE ingress?</p>

<p>Thanks in advance.</p>

<p>Eventually, to solve this problem, I've used ALB ingress controller group feature, which is currently in alpha state: <a href="https://github.com/kubernetes-sigs/aws-alb-ingress-controller/issues/914" rel="noreferrer">https://github.com/kubernetes-sigs/aws-alb-ingress-controller/issues/914</a></p>

<p>This is how my ingress resource looks now:</p>

<pre><code>---
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: myingress_1
  namespace: myns
  annotations:
    kubernetes.io/ingress.class: alb
    alb.ingress.kubernetes.io/scheme: internet-facing
    alb.ingress.kubernetes.io/tags: Environment=dev,Team=test
    alb.ingress.kubernetes.io/target-type: ip
    alb.ingress.kubernetes.io/group.name: mygroup
    alb.ingress.kubernetes.io/listen-ports: '[{"HTTP": 8088}]'
spec:
  rules:
    - host: &lt;HOST&gt;
      http:
        paths:
          - path: /*
            backend:
              serviceName: myservice
              servicePort: 8088
---
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: myingress_2
  namespace: myns
  annotations:
    kubernetes.io/ingress.class: alb
    alb.ingress.kubernetes.io/scheme: internet-facing
    alb.ingress.kubernetes.io/tags: Environment=dev,Team=test
    alb.ingress.kubernetes.io/target-type: ip
    alb.ingress.kubernetes.io/group.name: mygroup
    alb.ingress.kubernetes.io/listen-ports: '[{"HTTP": 60004}]'
spec:
  rules:
    - host: &lt;HOST&gt;
      http:
        paths:
          - path: /*
            backend:
              serviceName: myservice
              servicePort: 60004
</code></pre>

<p>where key thing is </p>

<pre><code>alb.ingress.kubernetes.io/group.name: mygroup
</code></pre>

<p>which connects these two ingress resources.</p>

<p>Therefore, I end up with following:</p>

<ul>
<li>Service with multiple (two) ports in k8s exposed with two separate ingress 
resources but they both point to the same AWS ALB (because of the same group 
name)</li>
<li>On the AWS ALB side, I get one ALB with two ports exposed: 8088 and
60004 and each of them points to same k8s service but
different port on the same pod (this could easily be two different k8s services 
if that was needed)</li>
</ul>
