ad54c5a278
Traefik should follow modern IT trends, and use manager/leader/worker/agent, etc. instead of "master/slave". e.g jenkinsci/jenkins#2007 (https://issues.jenkins-ci.org/browse/JENKINS-27268) NB: of course, it can only apply where possible, since backends like Mesos should retain their own concepts, and not add more confusion.
20 lines
914 B
Markdown
20 lines
914 B
Markdown
# Clustering / High Availability (beta)
|
|
|
|
This guide explains how tu use Træfik in high availability mode.
|
|
In order to deploy and configure multiple Træfik instances, without copying the same configuration file on each instance, we will use a distributed Key-Value store.
|
|
|
|
## Prerequisites
|
|
|
|
You will need a working KV store cluster.
|
|
|
|
## File configuration to KV store migration
|
|
|
|
We created a special Træfik command to help configuring your Key Value store from a Træfik TOML configuration file.
|
|
Please refer to [this section](/user-guide/kv-config/#store-configuration-in-key-value-store) to get more details.
|
|
|
|
## Deploy a Træfik cluster
|
|
|
|
Once your Træfik configuration is uploaded on your KV store, you can start each Træfik instance.
|
|
A Træfik cluster is based on a manager/worker model.
|
|
When starting, Træfik will elect a manager. If this instance fails, another manager will be automatically elected.
|
|
|