resilien
/
wesher
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Update README.md 

Co-authored-by: Leo Antunes <leo@costela.net>
This commit is contained in:
kaiyou 2020-05-18 10:15:52 +02:00 committed by Leo Antunes
parent 129291e848
commit e788b3eaef
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
README.md
View File

@ -148,12 +148,12 @@ All options can be passed either as command-line flags or environment variables:
## Running multiple clusters ## Running multiple clusters
Wesher supports having a node be a member of multiple clusters. The following settings must be explicitely set to non-conflicting values: ```suggestion
- `--interface`, so that wireguard does not mix up traffic, the interface name is also used for naming the state file To make a node be a member of multiple clusters, simply start multiple wesher instances. The following settings must be explicitly set to different values for each instance:
- `--cluster-port` or `--bind-addr` or `--bind-iface`, so that wesher can properly bind to its port - `--interface`
- `--wireguard-port`, so that wireguard can properly bind to its port - either `--cluster-port`, or `--bind-addr` or `--bind-iface`
- `--wireguard-port`
One should also use different overlay networks. Even though using the same network on different devices will work in some cases, it is not the intended use. - `--overlay-net` (optional, but recommended to avoid node address conflicts)
Finally, one should use different cluster keys for different clusters, as a security best practice. Finally, one should use different cluster keys for different clusters, as a security best practice.