Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🥳 aws-load-balancer-controller v2.4.7 Automated Release! 🥑 #905

Merged

Conversation

kishorj
Copy link
Contributor

@kishorj kishorj commented Feb 23, 2023

aws-load-balancer-controller v2.4.7 Automated Chart Sync! 🤖🤖

Release Notes 📝:

v2.4.7 (requires Kubernetes 1.19+)

Documentation

Image: public.ecr.aws/eks/aws-load-balancer-controller:v2.4.7

Thanks to all our contributors! 😊

Action Requrired

🚨 🚨 🚨 We've updated the reference IAM policies to explicitly add the AddTag permission for creating load balancer and listener resources. We recommend updating your controller IAM policies with the new permissions for existing installations as well.

Whats new

  • This patch release updates the controller to use discovery.k8s.io/v1 version of EndpointSlice for compatibility with k8s 1.25 and later releases. Starting this patch release, the controller will be able to support EndpointSlice in k8s 1.21 and later clusters only.
  • We have also updated the reference IAM policies to explicitly allow the AddTag permission for the ELBv2 CreateTargetGroup and CreateLoadBalancer. You will have to update the existing controller IAM permissions if you encounter the AccessDenied errors for the elbv2 APIs

Changelog since v2.4.5

@kishorj kishorj requested a review from M00nF1sh as a code owner February 23, 2023 16:49
@jdn5126 jdn5126 merged commit 23b2eb4 into aws:master Feb 23, 2023
Copy link
Member

@orsenthil orsenthil left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants