This commit fixes rafting and routing to the leader issues. #359
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #107
This commit makes a service for each pod by using the unique statefull
set name label. These services ensure that there is a cluster ip
reserved for each pod. The rafting uses these cluster ips.
Orchestrator will proxy/route traffic to its leader. So, the main
service can be used as entry point and all the trafic will be routed to
the leader.
See: https://github.com/github/orchestrator/blob/master/docs/configuration-raft.md
See: presslabs/docker-orchestrator#8
Signed-off-by: Kevin Hellemun [email protected]