🥳 aws-load-balancer-controller v2.7.0 Automated Release! 🥑 #1059
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
aws-load-balancer-controller v2.7.0 Automated Chart Sync! 🤖🤖
Release Notes 📝:
v2.7.0 (requires Kubernetes 1.22+)
Documentation
Image: public.ecr.aws/eks/aws-load-balancer-controller:v2.7.0
Thanks to all our contributors! 😊
Action required
We've updated the reference IAM policies to explicitly add the
elasticloadbalancing:DescribeTrustStores
permission for describing the trust stores resources to use the new mTLS feature for ingresses on controller. load balancer and listener resources. We recommend updating your controller IAM policies with the new permissions for your existing installations as well.Whats new
elasticloadbalancing:DescribeTrustStores
permission--service-target-eni-security-group-tags
to allow users to specify additional tags that should be used when the controller looks for the security group to use when adding ingress rules for NLB targetsEnhancement and Fixes
Changelog since v2.6.2