envoyproxy / envoyproxy/gateway
CTP should only configure client-side (downstream) connections, but its `http1` settings leak into the upstream cluster config — which is the only reason this PR has to treat CTP as cluster-scoped and demerge on it. Worth reconsidering whether upstream HTTP/1 belongs in BTP instead.
- Dominant language
- Go
- Stars
- 3k
- Forks
- 864
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 148
Description
Non-blocking, out of scope for this PR: CTP should only configure client-side (downstream) connections, but its `http1` settings leak into the upstream cluster config — which is the only reason this PR has to treat CTP as cluster-scoped and demerge on it. Worth reconsidering whether upstream HTTP/1 belongs in BTP instead.
_Originally posted by @zhaohuabing in https://github.com/envoyproxy/gateway/pull/9477#discussion_r3644051361_
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing PR #9477 and the linked discussion to understand how CTP is treated as cluster-scoped and where its http1 settings enter upstream cluster configuration. Trace the relevant CTP, BTP, and upstream HTTP/1 configuration paths, then determine and document the intended ownership and demerge behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, networking
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100