...

https://aws.amazon.com/elasticloadbalancing/pricing/?nc1=h_ls

Your AWS account has the following quotas related to Application Load Balancers.

https://docs.aws.amazon.com/elasticloadbalancing/latest/application/load-balancer-limits.html

The following quotas are for rules.

...

How we add data to it https://github.com/folio-org/pipelines-shared-library/blob/80b63af619da71ab8ada14eb5e074bfd3bbf4ebd/vars/helm.groovy

config[(module_name)]['ingress']['hosts'][0] += [host: domain]

Create load balancer add rules to it

...

Attach service to specific load balancer via group.

config[(module_name)]['ingress']['annotations'] += ['alb.ingress.kubernetes.io/group.name': "${project_config.getClusterName()}.${project_config.getProjectName()}"]

...

decrease alb

https://folio-dev.ci.folio.org/NamespaceName/ServiceName

1) When we create new cluster we should create new router53 record (service host).

2) When we will creating new namespace we must create ingress (public alb group may be in default namespace) with rule link to cluster host and new name space, before we create any ingresses in that namespace.

3) Create ingress in new namespace and use as host alb that was created in previous step.

Url example:

use only one static name for alb.ingress.kubernetes.io/group.name it allow to don't create a new alb for each namespace

config[(module_name)]['ingress']['annotations'] += ['alb.ingress.kubernetes.io/group.name': "${project_config.getClusterName()}.${project_config.getProjectName()}"]

Rules will be the same as current because we don't touch the Router53 records that has been creating by EKS .

We can reduce count records of Routers53 (Currently we pay for them about 4$).

For it we need to add into our ingress more http and modify the records.

For create new internal load balancer in Kubernetes 

kubernetes.io/ingress.class: nginx

for external alb need to change routing to internal nginx lb 
path: /namespace
backend:
  resource:
    apiGroup: k8s.example.com
    name: namespace

Conclusion

We have about 15 alb on dev env.

Image Added

In each of them 1 listener with about 17 rules that go to unique target group as result we have about 255 rules/target groups in limits we can see that we can increase count of rules but we can't increase the count of unique target group per alb.

I think it possible to increase this limit for us but for it we must communicate with AWS Support to ask them to ask their developers (because it hard code) increase this limit for us. For it we need to provide reasons why we need it and what the benefits it will give to us.