kubernetes-sigs/cluster-api-provider-aws

Make API Server classic load balancer Idle Timeout configurable by the user

Open

#2,844 opened on Oct 12, 2021

View on GitHub
 (10 comments) (0 reactions) (0 assignees)Go (689 forks)auto 404
help wantedkind/featurelifecycle/staleneeds-triagepriority/important-longterm

Repository metrics

Stars
 (723 stars)
PR merge metrics
 (PR metrics pending)

Description

/kind feature

Describe the solution you'd like The default idle timeout is 60s. In #516, we increased it to 10m. As a cluster admin, I may want to increase the timeout even more, e.g., to 60m.

Anything else you would like to add: The Network Load Balancer (NLB) does not have an idle timeout, but it was not a viable alternative last time we looked, which was in 2018 (https://github.com/kubernetes-sigs/cluster-api-provider-aws/pull/115#discussion_r220562864). Is NLB viable now?

Contributor guide

Research direction
Tech stack
Domain
Issue type
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Prerequisites
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.