envoy: Allow customize per cluster connections / requests limit#43049
envoy: Allow customize per cluster connections / requests limit#43049julianwiedmann merged 1 commit intocilium:mainfrom
Conversation
This comment was marked as resolved.
This comment was marked as resolved.
gandro
left a comment
There was a problem hiding this comment.
Helm-wise this looks good to me, thanks for your contribution!
Please make sure to sign off your commit (git commit --amend --sign-off).
|
I also notice that your PR description and commit message say the limit is increased, but the text mentions that the current default is 1024 and doesn't actually increase it. Please fix the commit and PR title. Also, it seems the the build is broken. Have you tested this commit? If so, how have you tested it? |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
sorry, I have change the commit message to 'Allow customize' |
|
Thanks! Please note that the build is still broken: |
|
The Helm schema also seems off (wrong order). Please run diff --git a/install/kubernetes/cilium/values.schema.json b/install/kubernetes/cilium/values.schema.json
index 5f19db7bbdc0..1f193890ff9d 100644
--- a/install/kubernetes/cilium/values.schema.json
+++ b/install/kubernetes/cilium/values.schema.json
@@ -2272,10 +2272,10 @@
"maxConcurrentRetries": {
"type": "integer"
},
- "maxConnections": {
+ "maxConnectionDurationSeconds": {
"type": "integer"
},
- "maxConnectionDurationSeconds": {
+ "maxConnections": {
"type": "integer"
},
"maxRequestsPerConnection": {
|
4036db7 to
134a51b
Compare
Please rebase to the top of |
|
/test |
Signed-off-by: exherb <[email protected]>
|
@exherb There's no need to rebase the branch except there are conflicts. Otherwise we have to continue re-running the test suite. |
|
sorry, I thought I have to rebase to merge. |
|
no problem. no, once the tests pass and the |
|
@mhofstetter #43455 is this back port pull request mergable? |
…ernal envoy While we have cilium#43049 to cover embedded case. This PR is to cover the external envoy use case to use maxConnections and maxRequests Signed-off-by: Liyi Huang <[email protected]>
While we have cilium#43049 to cover embedded case. This PR is to cover the external envoy use case to use maxConnections and maxRequests Signed-off-by: Liyi Huang <[email protected]>
While we have cilium#43049 to cover embedded case. This PR is to cover the external envoy use case to use clusterMaxRequests and clusterMaxConnections Signed-off-by: Liyi Huang <[email protected]>
While we have cilium#43049 to cover embedded case. This PR is to cover the external envoy use case to use clusterMaxRequests and clusterMaxConnections Signed-off-by: Liyi Huang <[email protected]>
While we have #43049 to cover embedded case. This PR is to cover the external envoy use case to use clusterMaxRequests and clusterMaxConnections Signed-off-by: Liyi Huang <[email protected]>
While we have cilium#43049 to cover embedded case. This PR is to cover the external envoy use case to use clusterMaxRequests and clusterMaxConnections Signed-off-by: Liyi Huang <[email protected]>
[ upstream commit 3efb667 ] While we have #43049 to cover embedded case. This PR is to cover the external envoy use case to use clusterMaxRequests and clusterMaxConnections Signed-off-by: Liyi Huang <[email protected]> Signed-off-by: Tom Hadlaw <[email protected]>
Envoy default limit on connections/requests on a cluster is 1024. This is not enough for large pod.
Please ensure your pull request adheres to the following guidelines:
description and a
Fixes: #XXXline if the commit addresses a particularGitHub issue.
Fixes: <commit-id>tag, thenplease add the commit author[s] as reviewer[s] to this issue.