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.

Sign up for GitHub

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

Jump to bottom

Support sticky sessions under SWARM Mode. #1024 #1033

Merged
merged 2 commits into from
Feb 6, 2017
Merged

Support sticky sessions under SWARM Mode. #1024 #1033

merged 2 commits into from
Feb 6, 2017

Commits on Feb 6, 2017

  1. Support sticky sessions under SWARM Mode. 

    SWARM Mode has it's own built in Load balancer, so if we want to leverage sticky sessions,
 or if we would just prefer to bypass it and go directly to the containers (aka tasks), via
	--label traefik.backend.disable.swarm.loadbalancer=true
 then we need to let Traefik know about the underlying tasks and register them as
 services within it's backend.
    @emilevauge
    Mike Foley authored and emilevauge committed Feb 6, 2017
    Configuration menu
    Copy the full SHA
    d2b47a5 View commit details
    Browse the repository at this point in the history

  2. Added service name to dockerData struct. 

    In Swarm mode with with Docker Swarm’s Load Balancer disabled (traefik.backend.loadbalancer.swarm=false)
service name will be the name of the docker service and name will be the container task name
(e.g. whoami0.1).  When generating backend and fronted rules, we will use service name instead of name if a
rule is not provided.

Initialize dockerData.ServiceName to dockerData.Name to support non-swarm mode.
    @emilevauge
    Mike Foley authored and emilevauge committed Feb 6, 2017
    Configuration menu
    Copy the full SHA
    e0a4c58 View commit details
    Browse the repository at this point in the history