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

Fix rafting issues. #8

Merged
merged 4 commits into from
Jul 26, 2019
Merged

Fix rafting issues. #8

merged 4 commits into from
Jul 26, 2019

Conversation

OGKevin
Copy link
Contributor

@OGKevin OGKevin commented Jun 24, 2019

This commit ensures that each pod has its own cluster IP service. This
makes sure that "pod ips" do not change. Fixes
presslabs/docker-orchestrator/#4.

Orchestrator can automatically route traffic to the leader. By making a
service that talks to all pods + using the right http advertise config
value.

Fixes #4
Fixes bitpoke/mysql-operator#107

OGKevin added 3 commits June 24, 2019 15:55
This commit ensures that each pod has its own cluster IP service. This
makes sure that "pod ips" do not change. Fixes
presslabs/docker-orchestrator/#4.

Orchestrator can automatically route traffic to the leader. By making a
service that talks to all pods + using the right http advertise config
value.

Fixes presslabs/docker-orchestrator/#4
Fixes bitpoke/mysql-operator#107
Copy link
Member

@AMecea AMecea left a comment

Choose a reason for hiding this comment

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

Thank you for this contribution! Nice work!

We recently (starting with version 0.3.0.rc.3 of the mysql-operator), dropped this orchestrator chart and merge it into the mysql-operator chart. We did this because they are tightly coupled.

I will merge this PR after I will test it, maybe someone uses this chart. But please open the same PR against mysql-operator chart.

@OGKevin
Copy link
Contributor Author

OGKevin commented Jun 25, 2019

Alright, ill open a MR in that repo as well 👍

calind pushed a commit to bitpoke/mysql-operator that referenced this pull request Jul 1, 2019
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]>
@OGKevin
Copy link
Contributor Author

OGKevin commented Jul 25, 2019

@AMecea shall we close this one because it got merged in the other repo or?

Copy link
Member

@AMecea AMecea left a comment

Choose a reason for hiding this comment

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

Let's merge it, maybe it will be useful for other people that use this chart.

Thanks @OGKevin !

@AMecea AMecea merged commit 2deb0b6 into presslabs:master Jul 26, 2019
@OGKevin OGKevin deleted the fix-107 branch July 26, 2019 08:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Use individual service for each orchestrator node Node unable to rejoin after failure
2 participants