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

GCE Multiple K8s DC C* Deployment - Networking #36

Open
chrislovecnm opened this issue Jun 12, 2016 · 6 comments
Open

GCE Multiple K8s DC C* Deployment - Networking #36

chrislovecnm opened this issue Jun 12, 2016 · 6 comments

Comments

@chrislovecnm
Copy link
Member

@paralin please submit a PR for getting muitple DC's Racks on GCE.

  1. Bash scripts for networking
  2. VPN Docker
  3. Documentation

Once you have submitted a PR, let me know and I can get you a baby k8s cluster.

@paralin
Copy link

paralin commented Jun 12, 2016

for rack I would just specify the rack name as the node attribute for availability zone

for DC most of what youre going to do is configuration in the GCE UI

@chrislovecnm
Copy link
Member Author

so nothing in GCE ui please. Please do all through gcloud api 😄

Bash is beautiful.

https://cloud.google.com/sdk/gcloud/

Or if you are really adventurous you can do terraform ...

@mward29
Copy link
Contributor

mward29 commented Jun 13, 2016

kubectl label nodes $PRIVATE_IP failure-domain.beta.kubernetes.io/region=$REGION
kubectl label nodes $PRIVATE_IP failure-domain.beta.kubernetes.io/zone=$AVAIL_ZONE

@chrislovecnm
Copy link
Member Author

@paralin have you worked out the networking as of yet with vpn?

@paralin
Copy link

paralin commented Jun 23, 2016

Yes it works. At least for the purpose of bridging 2 clusters.

@chrislovecnm
Copy link
Member Author

chrislovecnm commented Jun 23, 2016

@paralin when will you have a chance to document? I will mention on Monday that examples are coming for multiple physical Datacenter K8s installs with Multiple DC C*, are coming.

The demo will have two Datacenters btw. I stopped the custom seedprovider, and went to DNS. Do you know of a way to have nodetool use DNS rather than IPs? IPs are not guaranteed with PetSets ... we may have a challenge with Token ranges :(

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

No branches or pull requests

3 participants