Skip to content

Conversation

@KBaichoo
Copy link
Contributor

which helps leverage additional connection pools useful for ingress sidecar usage.

Commit Message: Http Filter: Add connection_pool_cardinality http filter
Additional Description: Mechanism described in https://static.sched.com/hosted_files/colocatedeventsna2025/81/Envoy%20%40%20Netflix.pptx.pdf slides 19-21
Risk Level: low
Testing: unit / integration / running in prod
Docs Changes: included
Release Notes: included
Platform Specific Features: n/a

additional connection pools useful for ingress sidecar usage.

Signed-off-by: Kevin Baichoo <[email protected]>
@repokitteh-read-only
Copy link

CC @envoyproxy/api-shepherds: Your approval is needed for changes made to (api/envoy/|docs/root/api-docs/).
envoyproxy/api-shepherds assignee is @mattklein123
CC @envoyproxy/api-watchers: FYI only for changes made to (api/envoy/|docs/root/api-docs/).

🐱

Caused by: #42281 was opened by KBaichoo.

see: more, trace.

Copy link
Member

@mattklein123 mattklein123 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm kind of confused when/why this is useful. Why do you need multiple connection pools vs. just better tuning of the connection pool itself? Can you add some high level docs for this filter in the arch section. and when/why someone would want to use it?

/wait

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants