Aws-load-balancer-controller: create new alb only if there isn't one already associated with the ingress host

[yawboateng]

Is it possible to have the controller to only create a new alb if there isn't one already associated with the ingress host?

reason:
I have one hostname, but the services I want to create rules for are in different namespaces, so I'm using multiple ingress objects, but each ingress object creates a new alb and updates the route53 DNS record to the point the most recent one

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: ingress-namespaceAuth
  namespace: auth
spec:
  rules:
  - host: apps.example.com
    http:
      paths:
      - path: /service1InAuthNS/*
        backend:
          serviceName: service1
          servicePort: 443
      - path: /service2InAuthNS/*
        backend:
          serviceName: service2
          servicePort: 443

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: ingress-namespaceMonitoring
  namespace: monitoring
spec:
  rules:
  - host: apps.example.com
    http:
      paths:
      - path: /service3InMonitoringNS/*
        backend:
          serviceName: service3
          servicePort: 443
     - path: /
        backend:
          serviceName: service4
          servicePort: 443

[joshrosso]

Today you can't. Each ingress resource represents a new ALB.

However, these seems reasonable and would add some great flexibility into the controller's usage.

We should consider it for #11.

[treyhyde]

11 and one ALB per ingress is what makes this project interesting (to me).

[yawboateng]

Thanks @joshrosso, looking forward to this. Will also give us the flexibility of using the alb.ingress.kubernetes.io/backend-protocol annotation to configure both HTTPS and HTTP targetGroup protocols on one alb

[joshrosso]

Unfortunately, I don't see this making it to 1.0, although we will have host based routing.

Going to slate it for 1.1 as it's still a cool idea, just makes mapping quite a bit more complex.

[whithajess]

Using Helm templating for all our applications, and it seems creating an ingress file per chart is how it does it. But a $20 per month ALB per app seems expensive so this would definitely be better in my mind.

[pperzyna]

@joshrosso Any update?

[whithajess]

Seems related: https://github.com/coreos/alb-ingress-controller/issues/298

[bigkraig]

Closing this and tracking the feature request in #298