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.

Sign up for GitHub

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

Jump to bottom

Configure master node same as slave node #4128

Closed
dchen1107 opened this issue Feb 4, 2015 · 4 comments
Closed

Configure master node same as slave node #4128

dchen1107 opened this issue Feb 4, 2015 · 4 comments
Labels
priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/node Categorizes an issue or PR as relevant to SIG Node.
Milestone
v1.0

Comments

@dchen1107
Copy link
Member

This is pre-requirement for running all master components in a pod. #3853 was filed to run etcd as a pod. To make sure we really run etcd as a pod using Kubernete network model without specifying HostPort from spec, we need config the master node:

  1. create networking bridge called cbr0
  2. config docker run with "--bridge cbr0 --iptables=false"
  3. add default route for master node (on GCE). Need to figure out other cloud providers.
@dchen1107 dchen1107 added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/node Categorizes an issue or PR as relevant to SIG Node. team/cluster labels Feb 4, 2015
@dchen1107
Copy link
Member Author

cc/ @ArtfulCoder @thockin

@zmerlynn
Copy link
Member

zmerlynn commented Feb 4, 2015

Or finally switch to flannel. :)

On Wed Feb 04 2015 at 1:22:43 PM Dawn Chen notifications@github.com wrote:

cc/ @ArtfulCoder https://github.com/ArtfulCoder @thockin
https://github.com/thockin

—
Reply to this email directly or view it on GitHub
#4128 (comment)
.

@dchen1107 dchen1107 added this to the v1.0 milestone Feb 18, 2015
@dchen1107 dchen1107 mentioned this issue Feb 23, 2015
Merged
This was referenced Mar 12, 2015
Merged
Merged
@brendandburns
Copy link
Contributor

This is now done for GCE and GKE. We need to do it for AWS (and others?)

@brendandburns
Copy link
Contributor

Marking this done, as of #5892 we now configure AWS, GCE and GKE this way.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/node Categorizes an issue or PR as relevant to SIG Node.
Projects
None yet
Milestone
v1.0
Development

No branches or pull requests
4 participants
@zmerlynn @thockin @brendandburns @dchen1107