aws-load-balancer-controller: v2.8.0 #1105
Merged
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.
v2.8.0 (requires Kubernetes 1.22+)
Documentation
Image: public.ecr.aws/eks/aws-load-balancer-controller:v2.8.0
Thanks to all our contributors! 😊
Action required
We have added
certificateArn
and updatedipAddressType
fields in IngressClassParams, and addedvpcID
field in TargetGroupBinding. If you are upgrading the charts using helm upgrade, you need to update CRDs manuallykubectl apply -k https://github.com/aws/eks-charts/blob/master/stable/aws-load-balancer-controller/crds/crds.yaml
ALB mTLS is now available in the China partition. 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. If you want to use the ALB mTLS feature in China region, updating your controller IAM policies with the new permissions.Whats new
certificateArn
for Ingress at the IngressClass level. This feature adds newcertificateArn
to the IngressClassParams Spec to configure the ARN of the certificates for all Ingresses that belong to IngressClass with this IngressClassParams.dualstack-without-public-ipv4
to allow customers to provision load balancers without IPv4s for clients that can connect using just IPv6s. For example, users can choose a dualstack ALB without public IPv4 when setting up a new internet facing ALB, or switch to dualstack without public IPv4 for an existing internet facing ALB by specifyingalb.ingress.kubernetes.io/ip-address-type: dualstack-without-public-ipv4
. To set theipAddressType
for ingress at the IngressClass level, addipAddressType: dualstack-without-public-ipv4
to the IngressClassParams Spec. See AWS Launch What's New Post about this feature.aws-load-balancer-inbound-sg-rules-on-private-link-traffic
to configure whether to apply security group rules to traffic sent to the load balancer through AWS PrivateLink.vpcID
to the TargetGroupBinding Spec to allow registration in target groups that are created with in a VPC that is different from the cluster VPC. If thevpcID
is unspecified, the controller will fetch the clustervpcID
by default.alb.ingress.kubernetes.io/security-group-prefix-lists
andservice.beta.kubernetes.io/aws-load-balancer-security-group-prefix-lists
to ensure the security group attached to the load balancer can allow access from the specified Managed Prefix List. The annotation will be ignored ifalb.ingress.kubernetes.io/security-groups
orservice.beta.kubernetes.io/aws-load-balancer-security-groups
is present.Enhancement and Fixes
Changelog since v2.7.2