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

Enable loadbalancer.sticky for Consul Catalog #1917

Merged
merged 3 commits into from
Aug 24, 2017

Conversation

nbonneval
Copy link
Contributor

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

@nbonneval nbonneval changed the title Enable loadbalancer.sticky for Consul Catalo (#1575) Enable loadbalancer.sticky for Consul Catalog (#1575) Aug 4, 2017
@ldez ldez changed the title Enable loadbalancer.sticky for Consul Catalog (#1575) Enable loadbalancer.sticky for Consul Catalog Aug 4, 2017
@ldez ldez added this to the 1.4 milestone Aug 10, 2017
@ldez ldez added the size/S label Aug 16, 2017
Copy link
Contributor

@nmengin nmengin left a 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?

@nbonneval
Copy link
Contributor Author

@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...

Copy link
Contributor

@nmengin nmengin left a 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! 😉

Copy link
Contributor

@nmengin nmengin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Contributor

@ldez ldez left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Contributor

@ldez ldez left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

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

Successfully merging this pull request may close these issues.

5 participants