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 environment variables to configure HTTP/2 keepalive timeout and interval configuration from environment variables #2803

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

UsingCoding
Copy link

@UsingCoding UsingCoding commented Mar 16, 2024

Add environment variables to configure HTTP/2 keepalive timeout and interval

Problem
There is no way to configure timeout and interval via environment variables.

Solution
Configure keepalive timeout and interval for inbound/outbound by LINKERD2_PROXY_{INBOUND,OUTBOUND}_HTTP2_KEEPALIVE_{TIMEOUT,INTERVAL}

Fixes linkerd/linkerd2#12269

Add environment variables to configure HTTP/2 keepalive timeout and interval

Problem
There is no way to configure timeout and interval via environment variables

Solution
Add environment variables to configure HTTP/2 keepalive timeout and interval

Validation

Fixes #[12269]

Signed-off-by: UsingCoding <extendedmoment@outlook.com>
@UsingCoding UsingCoding requested a review from a team as a code owner March 16, 2024 12:45
…s still possible to specify the timeout for HTTP/2 separately

Signed-off-by: UsingCoding <extendedmoment@outlook.com>
…control plane.

The keepalive timeout for the control plane should be different than for proxy connections

Signed-off-by: UsingCoding <extendedmoment@outlook.com>
@olix0r
Copy link
Member

olix0r commented Mar 26, 2024

@UsingCoding thanks. I've been waiting to sync up with more of the team on how to proceed here. The environment-based approach is really not how we want to expose this sort of configuration, ultimately -- it's the wrong granularity of configuration. We should really be configuring this per server and per client (and not on the workload broadly). So we've treated the environment variables as a developer escape hatch for testing and never really wanted to show this configuration directly to users.

That said, adding non-environment configuration is quite a bit more work, so I'm sympathetic to simply exposing what we have today.

I'll talk to the team and come back with clearer guidance on how to proceed.

UsingCoding added a commit to ispringtech/linkerd2-proxy that referenced this pull request Mar 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants