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

Begin to separate out the etcd cluster and the master clusters #50

Open
wants to merge 14 commits into
base: master
Choose a base branch
from

Conversation

mirthy
Copy link
Contributor

@mirthy mirthy commented Aug 25, 2016

Do not merge yet, testing separating out the master/controller from etcd.

@wellsie
Copy link
Member

wellsie commented Aug 25, 2016

Tack started out that way ;) I merged etcd with k8s masters a while back -
mainly to cut down on under utilized instances. I also liked the idea of
the apiservers being really close to etcd.

It will be nice to have both options available.
On Wed, Aug 24, 2016 at 8:56 PM Jeff Kwan [email protected] wrote:

Do not merge yet, testing separating out the master/controller from etcd.

You can view, comment on, or merge this pull request online at:

#50
Commit Summary

  • Begin to separate out the etcd cluster and the master clusters

File Changes

Patch Links:


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#50, or mute the thread
https://github.com/notifications/unsubscribe-auth/AE6-kY6Je7tkeWuwNkE5pn2zCtvrj37hks5qjRJhgaJpZM4JsrBf
.

@mirthy
Copy link
Contributor Author

mirthy commented Aug 25, 2016

I ran into this thinking about how to handle upgrades on the api server side without rebuilding the cluster entirely.

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.

2 participants