🥳 aws-load-balancer-controller v2.4.0 Automated Release! 🥑 #19
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.4.0 Automated Chart Sync! 🤖🤖
Release Notes 📝:
v2.4.0 (requires Kubernetes 1.19+)
Documentation
Image: docker.io/amazon/aws-alb-ingress-controller:v2.4.0
Thanks to all our contributors! 😊
Note
This release uses the new Ingress API version networking.k8s.io/v1 available in kubernetes 1.19 and later releases. As a result, the v2.4.0 and later releases of the
aws-load-balancer-controller
will not support kubernetes 1.18 and older versions. If you are running the older k8s version, you can either upgrade your cluster or use the v2.3.x version of the controller.IMPORTANT If you are upgrading the controller from a prior version to v2.4.0, please apply the entire manifest or use helm due to the webhook changes.
For convenience, the v2.4.0 release manifest and the helm chart creates an
IngressClass
resource namedalb
by default.What's new
spec.loadBalancerClass
keepTLSSecret
is true by defaultServiceTypeLoadBalancerOnly
which can optionally limit the controller to service of typeLoadBalancer
Bug fixes
Changelog since v2.3.1
ECR images