aws-load-balancer-controller
aws-load-balancer-controller copied to clipboard
kubernetes-sigs
Option to split ingress group to work around rule count limit
Is your feature request related to a problem? I have a load balancer ingress group that has grown past 100 rules.
Describe the solution you'd like I would like the option to split a large group across multiple LBs.
Describe alternatives you've considered I see this issue which has gone stale.
@jcogilvie, unfortunately, we do not have a good mechanism to split the ingress group when the listener rules exceed the 100 limit. We do plan to merge the ingress rules as a mitigation. see: https://github.com/kubernetes-sigs/aws-load-balancer-controller/issues/3446#issuecomment-1897609277
I would like to +1 this. The IngressGroups are an amazing feature but if it were possible to define a large number of Ingress resources and the aws-load-balancer-controller takes care of splitting it up into multiple ALBs when limits are hit, that would really take it to the next level. We currently manage this division manually and it's cause for problems when you're near the limits.
Listener rules are not the only limit we run into, but also limits with the number of ACM certificates per ALB are a possible problem that ideally the aws-load-balancer-controller could work around.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle stale - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle stale - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale