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

configurable HAProxy defaults #280

Closed
joshk0 opened this issue Jul 7, 2017 · 2 comments
Closed

configurable HAProxy defaults #280

joshk0 opened this issue Jul 7, 2017 · 2 comments

Comments

@joshk0
Copy link
Contributor

joshk0 commented Jul 7, 2017

We're trying to migrate away from a legacy HAProxy config. Our use case is extremely high volume of HTTP traffic, so low timeout values are very important. Here's what we have:

  timeout connect 5s
  timeout queue 5s
  timeout client 60s
  timeout server 60s
  timeout http-request 15s
  timeout http-keep-alive 2s

Unfortunately, defaults are as follows, and not configurable at the ingress object level (literally they are hardcoded in the template:)

    # Maximum time to wait for a connection attempt to a server to succeed.
    timeout connect         50000

    # Maximum inactivity time on the client side.
    # Applies when the client is expected to acknowledge or send data.
    timeout client          50000

    # Inactivity timeout on the client side for half-closed connections.
    # Applies when the client is expected to acknowledge or send data
    # while one direction is already shut down.
    timeout client-fin      50000

    # Maximum inactivity time on the server side.
    timeout server          50000

    # timeout to use with WebSocket and CONNECT
    timeout tunnel          50000

It would be nice to be able to configure these defaults in ExtendedIngress mode.

@joshk0
Copy link
Contributor Author

joshk0 commented Jul 7, 2017

What if this were exported to a configmap, and the configmap to use as the template can be selected by the ingress object?

@joshk0 joshk0 changed the title configurable default timeouts configurable HAProxy defaults Jul 7, 2017
@tamalsaha
Copy link
Contributor

What if this were exported to a configmap, and the configmap to use as the template can be selected by the ingress object?

I don't think that is practical since we regenerate the template based on Kube watcher. But we can add more annotations for this type of things.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants