v2.11.0 (requires Kubernetes 1.22+)
Documentation
Image: public.ecr.aws/eks/aws-load-balancer-controller:v2.11.0
Thanks to all our contributors! 😊
Action required
🚨 🚨 🚨 We’ve added new fields for capacity unit reservation on IngressClassParams. We’ve also added the targetGroupName field to the TargetGroupBinding which users can set in order to fetch targetGroup by Name instead or ARN. Make sure to update the CRD definition in your cluster. If you're upgrading the charts using helm upgrade, you need to update CRDs manually: kubectl apply -k "github.com/aws/eks-charts/stable/aws-load-balancer-controller/crds?ref=master"
We've updated the reference IAM policies to explicitly add the elasticloadbalancing:DescribeCapacityReservation and elasticloadbalancing:ModifyCapacityReservation permissions for describing and modifying capacity reservation. Please be sure to apply the latest IAM policy when upgrading.
What’s new
- Support Load balancer Capacity Unit Reservation for ALB and NLBs.
- Application Load Balancer (ALB) and Network Load Balancer (NLB) now support Load Balancer Capacity Unit (LCU) Reservation that allows you to proactively set a minimum capacity for your load balancer, complementing its existing ability to auto-scale based on your traffic pattern. For more info checkout what’s new post.
Enhancement and Fixes
- Add support to set the default load balancer scheme at the controller level
- TargetGroupBinding now support targetGroupName
- Bug fix: EnablePrefixForIpv6SourceNat is only applicable to NLB
Changelog since v2.10.1
- fix failing test (#3976, @zac-nixon)
- Update owners of the project (#3975, @shraddhabang)
- fix: EnablePrefixForIpv6SourceNat is only applicable to NLB (#3958, @wweiwei-li)
- Add support for capacity unit reservation for load balancers (#3950, @shraddhabang)
- Add —default-load-balancer-scheme command line flag (#3908, @phuhung273)
- TargetGroupBinding now support targetGroupName - #2655 refresh (#3903, @fatmcgav)