Open nirroz93 opened 11 months ago
It would be nice to see this implemented :+1: It would partially solve this one https://github.com/kubernetes-sigs/aws-load-balancer-controller/issues/1784 too.
Thanks for bringing this up, I think it's a good improvement to have. I think we can have the controller to merge the paths for each ingress if:
For example, when creating an ingress with the following spec:
spec:
rules:
- http:
paths:
- path: /test1
pathType: ImplementationSpecific
backend:
service:
name: my_service
port:
number: 80
- path: /test2
pathType: ImplementationSpecific
backend:
service:
name: my_service
port:
number: 80
- http:
paths:
- path: /*
pathType: ImplementationSpecific
backend:
service:
name: my_service
port:
number: 80
The controller is generating three rules right now:
With the change the controller will only generate one rule:
/kind feature
What is the maximum number of characters (or clauses) that can be merged into a single matcher line? If a rule would exceed it, it should be split into multiple rules at some boundary.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
/assign
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
Is your feature request related to a problem? Let's say we have the following (I used use-annotation, but it doesn't matter)
This will create 2 Load Balancer rules on the load balancer, the first with condition:
and the second with condition:
However, it could have created only 1 rule with condition
Creating multiple rules increase the rules evaluation (and therefore creates additional costs), and it's also less clear. Describe the solution you'd like Combine ingress rules with the same settings but different prefix\host to one rule
Describe alternatives you've considered Creating multiple LBs to avoid the extra evaluations costs