Merge ALB rules by the same host

[michaelkoro]

Is your feature request related to a problem?
We would like to be able to merge rules in the ingress resource, on the ALB level.

For example, when creating the following -

spec:
  rules:
    - http:
        paths:
          - path: /test1
            pathType: ImplementationSpecific
            backend:
              service:
                name: service_name
                port:
                  number: 80
          - path: /test2
            pathType: ImplementationSpecific
            backend:
              service:
                name: service_name
                port:
                  number: 80
    - http:
        paths:
          - path: /*
            pathType: ImplementationSpecific
            backend:
              service:
                name: service_name
                port:
                  number: 80

We want the controller to merge the two paths in the first rule, and create one rule in the ALB.
We are aware of the conditions annotation, but unfortunately working with it dynamically is very complicated.
Is there an easier way?

[kishorj]

@michaelkoro, we can optimize in limited situations - for consecutive rules so as to honor the ingress group order. Also the current ALB limit is max 5 conditions per rule.

Are you hitting the rules quotas or have other concerns?

/kind feature

[acgs771126]

+1, maybe this feature can prevent hit AWS ELB listener rule api throttle

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[benjefferies]

+1 would be great to see this in v2.6.0

[omerap12]

/assign

[henryzhao95]

+1, would love to see multiple hostnames with same backing service grouped together!

spec:
  ingressClassName: group1
  rules:
    - host: bar.api.internal
      http:
        paths:
        - pathType: Prefix
          path: "/"
          backend:
            service:
              name: awesome-service
              port:
                number: 443
    - host: foo.api.internal
      http:
        paths:
        - pathType: Prefix
          path: "/"
          backend:
            service:
              name: awesome-service
              port:
                number: 443