Adjust Ingress Gateway Configuration
- Dominant language
- Go
- Stars
- 30.1k
- Forks
- 4.6k
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 43
Description
When Envoy is acting as a front proxy there is some additional recommended configuration:
https://www.envoyproxy.io/docs/envoy/latest/configuration/best_practices/edge
Since adjusting these values currently requires using an escape hatch, we should improve the defaults we set for them.
From using at some user reports about improving throughput, this is another value to update:
https://www.envoyproxy.io/docs/envoy/latest/api-v2/api/v2/listener.proto#reuse_port
Contributor guide
Research direction
Start with the Envoy edge best-practices and reuse_port links in the issue, then trace Consul's ingress gateway defaults and the escape-hatch configuration that currently controls them. Done means the recommended front-proxy settings, including reuse_port, are applied by default and the affected configuration behavior is verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100