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

Support modifying http2 listener settings #3048

Closed
2 tasks done
arkodg opened this issue Mar 28, 2024 · 4 comments
Closed
2 tasks done

Support modifying http2 listener settings #3048

arkodg opened this issue Mar 28, 2024 · 4 comments
Assignees
Labels
area/api API-related issues
Milestone

Comments

@arkodg
Copy link
Contributor

arkodg commented Mar 28, 2024

Description:

Describe the desired behavior, what scenario it enables and how it

As a user, I'd like to increase the current defaults of these below settings for my setup
Defaults are derived from https://www.envoyproxy.io/docs/envoy/latest/configuration/best_practices/edge#configuring-envoy-as-an-edge-proxy

[optional Relevant Links:]

Any extra documentation required to understand the issue.

@arkodg arkodg added the triage label Mar 28, 2024
@guydc
Copy link
Contributor

guydc commented Mar 28, 2024

+1

@arkodg
Copy link
Contributor Author

arkodg commented Mar 28, 2024

@guydc does this fall into connection or a new http2 field within https://gateway.envoyproxy.io/latest/api/extension_types/#clienttrafficpolicyspec ?

@guydc
Copy link
Contributor

guydc commented Mar 28, 2024

I think that a new http2 field would be more appropriate.

@arkodg
Copy link
Contributor Author

arkodg commented Mar 28, 2024

discussed this in the meeting today, http2 seems like a popular option, will go with this in the init PR

@arkodg arkodg self-assigned this Mar 28, 2024
@arkodg arkodg added area/api API-related issues and removed triage labels Mar 28, 2024
@arkodg arkodg assigned zhaohuabing and unassigned arkodg Apr 19, 2024
@arkodg arkodg added this to the v1.1.0-rc1 milestone Apr 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/api API-related issues
Projects
None yet
Development

No branches or pull requests

3 participants