Skip to content
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

Allow configuring options for each server entry #516

Closed
julianvmodesto opened this issue Sep 20, 2017 · 3 comments

Comments

Projects
None yet
4 participants
@julianvmodesto
Copy link
Contributor

commented Sep 20, 2017

For all server entries in the HAProxy config, I would like to manage 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.

@tamalsaha

This comment has been minimized.

Copy link
Member

commented Sep 21, 2017

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)

@tamalsaha

This comment has been minimized.

Copy link
Member

commented Sep 25, 2017

Example:
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.

@tamalsaha

This comment has been minimized.

@tamalsaha tamalsaha added this to the 4.0.0 milestone Oct 4, 2017

@sadlil sadlil referenced this issue Oct 6, 2017

Merged

Limit Connections #571

@tamalsaha tamalsaha closed this Oct 6, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.