We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
For all server entries in the HAProxy config, I would like to manage maxconn.
maxconn
For example:
server pod-100.103.160.82 100.103.160.82:8080 maxconn 1000 server pod-100.112.130.212 100.112.130.212:8080 maxconn 1000
This would be possible if we allowed templating or adding options to the server directive.
server
The text was updated successfully, but these errors were encountered:
We were planning to support this via annotations on pod. This will be similar to how the backend weight works currently.
Also related #491 (limit-* annotations)
Sorry, something went wrong.
Example: ingress.appscode.com/max-connections: 3000
ingress.appscode.com/max-connections: 3000
If applied on Ingress, this will be set as the global maxconn
If applied to Pod (via Deployment, etc), this will be on the server line like backend weight.
limit-rps* - Rate limiting: http://www.haproxy.com/blog/use-a-load-balancer-as-a-first-row-of-defense-against-ddos/
No branches or pull requests
For all server entries in the HAProxy config, I would like to manage
maxconn
.For example:
This would be possible if we allowed templating or adding options to the
server
directive.The text was updated successfully, but these errors were encountered: