Open alexangas opened 2 years ago
Action required from @Azure/aks-pm
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Is your feature request related to a problem? Please describe. When setting
loadBalancerSourceRanges
for a service, each entry in the array appears to create a separate NSG rule. As there is one NSG shared by the AKS cluster, multiple services requiring this setting can quickly hit the NSG 1000 rule limit.Describe the solution you'd like Change the NSG rule creation logic such that there is a single rule per
loadBalancerSourceRanges
configuration. Within the rule, the array of IP addresses is populated. If my reading of the networking limits is correct, 4000 addresses within a rule should be allowed.Describe alternatives you've considered Not use
loadBalancerSourceRanges
at all and instead rely on features of third party tooling (e.g. the nginx-ingress whitelist-source-range annotation).Additional context Testing performed by setting controller.service.loadBalancerSourceRanges on the k8s ingress-nginx Helm chart.