-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
Enable loadbalancer.sticky for Consul Catalog #1917
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@nbonneval Many thanks for this PR.
Just a question, in the directory example, there is a compose file which allows to create a Docker consul container (compose-consul.yml) and a shell script which executes HTTP requests to this container(consul-config.sh).
Do you think this file has to be updated in the way to add request to the sticky attribute?
@nmengin Never thought about it, but why not. I did think about adding specific tests in provider/consul/consul_catalog_test.go though, but never took time to do it... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@nbonneval Thank you for your feedback.
I think it can be nice to add it.can you do it?
Specific test should be great! 😉
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Description
As commented by my colleague dwarfaz in the issue #1575, we added support for the backend.loadbalancer.sticky tag with consul_catalog by editing the provider's template.
It now always creates the backend's loadbalancer configuration section, with default values if nothing's specified, but supports changing both the load balancing method and the sticky flag.
In order to synchronize with other providers' capabilities & doc, I'd prefer the existing tag (backend.loadbalancer) to be renamed to backend.loadbalancer.method, but it would break existing configurations