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

AWS networking proposal #1255

Closed
wants to merge 1 commit into from
Closed

AWS networking proposal #1255

wants to merge 1 commit into from

Conversation

ragnard
Copy link
Contributor

@ragnard ragnard commented Sep 10, 2014

A document describing different ways of satisfying the Kubernetes networking model on AWS.

Currently describes how I managed to get things running. Would be grateful for feedback/improvements/alternative solutions etc.

@ragnard ragnard mentioned this pull request Sep 10, 2014
Closed
Ch00k added a commit to Ch00k/kubernetes that referenced this pull request Sep 10, 2014
@Ch00k
Add cluster validation routines. Make changes according to kubernetes…
50b697f 
…#1255
@smarterclayton
Copy link
Contributor

@rajatchopra/@Mrunal can you guys review?

@brendandburns
Copy link
Contributor

LGTM, given my perusal of the corresponding AWS docs, this seems correct. I don't have any concrete experience with AWS, would be great if someone who does could verify, but if we don't get validation in today let's just merge this, and take patches if there are problems.

@ragnard
Copy link
Contributor Author

ragnard commented Sep 10, 2014

TBH, the intention when I put this together was more to have a base for discussing different potential solutions/tradeoffs. An option would be to wait until #1230 is in a good state (looking quite good already) and merged and update this to reflect the actual approach used.

@jbeda
Copy link
Contributor

jbeda commented Sep 13, 2014

@ragnard -- this looks reasonable to me. This is very similar to how we do this in GCE with advanced routing. I'm not sure about AWS, but I'd look for limits on the number of routes you can have. The number of routes will scale with the number of nodes.

Also, there is nothing magic about the CIDRs assigned to the nodes. We picked 10.244.x.0/24 as it is close to the default IP range for GCE (10.240.0.0/16).

@bgrant0607
Copy link
Member

@ragnard @Ch00k What is the status of this and #1230? Do you plan to integrate this proposal as code into #1230?

Also, you should look at #1532, which will make a number of changes to the turnup scripts.

@bgrant0607 bgrant0607 added cluster/install kind/documentation Categorizes issue or PR as related to documentation. labels Oct 3, 2014
brendandburns pushed a commit to brendandburns/kubernetes that referenced this pull request Nov 10, 2014
@Ch00k @brendandburns
AWS support draft
1ff79fd 
Fix calling function before declaration

Set Name tags on instances

Hide import-key-pair error

Fix instances names resolution

Implement kube-down for AWS provider

Add cluster validation routines. Make changes according to kubernetes#1255

Implement post-deployment cluster validation

Set proper master name in userdata scripts

Fix kube-down path in hint

Add getting started for AWS
@brendandburns
Copy link
Contributor

I'm closing this, as we now have functioning AWS support via both flannel and vpc routes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
kind/documentation Categorizes issue or PR as related to documentation.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
5 participants
@ragnard @smarterclayton @brendandburns @jbeda @bgrant0607