chore: remove comments about MaxRequests or MaxPendingRequests only applying to particular HTTP version#57705
Conversation
…pplying to particular HTTP version The circuit-breaker connection pool settings `MaxRequests`and `MaxPendingRequests` apply to HTTP/1.1 as well as HTTP/2 since [1] and [2]. This was actually changed in the Istio docs via [3], but these source code comments were left, potentially causing confusion. [1] envoyproxy/envoy#9215 [2] envoyproxy/envoy#9668 [3] istio/api#2428 Signed-off-by: Christian Rohmann <christian.rohmann@inovex.de>
|
😊 Welcome @frittentheke! This is either your first contribution to the Istio istio repo, or it's been You can learn more about the Istio working groups, Code of Conduct, and contribution guidelines Thanks for contributing! Courtesy of your friendly welcome wagon. |
|
Hi @frittentheke. Thanks for your PR. I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
/ok-to-test |
|
/test integ-ambient-nftables |
|
@frittentheke: The following test failed, say
DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
Is there anything I can do to have the test pass? |
You can ignore the |
|
/test integ-ambient-dual |
Please provide a description of this PR:
The circuit-breaker connection pool settings
MaxRequestsandMaxPendingRequestsapply to HTTP/1.1 as well as HTTP/2 since [1] and [2].This was actually changed in the Istio docs via [3], but these source code comments were left, potentially causing confusion.
[1] envoyproxy/envoy#9215
[2] envoyproxy/envoy#9668
[3] istio/api#2428