-
Notifications
You must be signed in to change notification settings - Fork 301
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
feat(proxy): introduce Concurrency under EnvoyProxy resource #1719
Conversation
cc: @zirain |
Codecov Report
@@ Coverage Diff @@
## main #1719 +/- ##
==========================================
+ Coverage 64.77% 64.94% +0.16%
==========================================
Files 83 83
Lines 11925 11930 +5
==========================================
+ Hits 7725 7748 +23
+ Misses 3715 3702 -13
+ Partials 485 480 -5
|
d8cacd1
to
14cf30b
Compare
Signed-off-by: Ardika Bagus <me@ardikabs.com>
14cf30b
to
f79db5c
Compare
f529612
to
f009c23
Compare
@ardikabs looks like you also need to run |
Signed-off-by: Ardika Bagus <me@ardikabs.com>
f009c23
to
647fda3
Compare
@arkodg yes, i missed the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM thanks !
lets wait until v0.5 lands to merge this PR, since this PR introduces doc changes
What type of PR is this?
Introduce an additional field under
EnvoyProxy
for additional proxy-level configuration options. The idea should be similar to Istio's ProxyConfig.What this PR does / why we need it: Our use case demands configuring the non-default concurrency for the Envoy proxy which currently is not supported by Envoy Gateway.
Which issue(s) this PR fixes: #1718
Fixes #