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

Add Idle Timeout support for NLB #1023

Open
JoelSpeed opened this issue Sep 17, 2024 · 1 comment
Open

Add Idle Timeout support for NLB #1023

JoelSpeed opened this issue Sep 17, 2024 · 1 comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@JoelSpeed
Copy link
Contributor

What would you like to be added:

AWS recently announced the ability to configure the NLB TCP Idle Timeout. Up until now the default value has been 350 seconds, but for ELBs the default is 60 seconds, and is also configurable using the service.beta.kubernetes.io/aws-load-balancer-connection-idle-timeout annotation.

We should extend the annotation implementation so that it also works for the NLB implementation of EnsureLoadBalancer to gain access to this new functionality from AWS.

Why is this needed:

Support new features from AWS, improve consistency between ELB and NLB implementations.

/kind feature

@k8s-ci-robot k8s-ci-robot added kind/feature Categorizes issue or PR as related to a new feature. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Sep 17, 2024
@kmala
Copy link
Member

kmala commented Sep 23, 2024

/triage accepted

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Sep 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

3 participants