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

Private topology with kubenet networking #1335

Closed
jonchiu opened this issue Jan 3, 2017 · 5 comments
Closed

Private topology with kubenet networking #1335

jonchiu opened this issue Jan 3, 2017 · 5 comments
Labels
area/documentation good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. kind/support Categorizes issue or PR as a support question.
Milestone
1.5.1

Comments

@jonchiu
Copy link
Contributor

jonchiu commented Jan 3, 2017

I noticed that during cluster creation, kubenet is not supported if a private topology is specified. (https://github.com/kubernetes/kops/blob/master/cmd/kops/create_cluster.go#L645)

Can you enlighten me as to why this isn't allowed. I'm happy to add this to the documentation.

Thanks!
@chrislovecnm
Copy link
Contributor

@jonchiu internal services do not work with kubenet routing. I am not certain exactly why, but it is probably because of routing between AZ.

@justinsb / @kris-nova can you shed more light?

@justinsb
Copy link
Member

justinsb commented Jan 4, 2017

It's because:

  • we expect most people running private are the more advanced users that will also be running multi AZ
  • NAT gateways are single AZ
  • You need to wire up a routing table per AZ to use NAT gateways
  • kubenet with VPC networking requires a single routing table

@chrislovecnm
Copy link
Contributor

@jonchiu would love you to document the above!

@chrislovecnm chrislovecnm added area/documentation Help Wanted! kind/support Categorizes issue or PR as a support question. labels Jan 4, 2017
@justinsb justinsb modified the milestone: 1.5.0 Jan 5, 2017
@jonchiu jonchiu mentioned this issue Mar 5, 2017
Merged
@chrislovecnm
Copy link
Contributor

Closing

@AndresPineros
Copy link

So, why not allowing kubenet with private topology for a single AZ?

@tsuna tsuna mentioned this issue Mar 6, 2019
Closed
@rifelpet rifelpet added good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. and removed good-starter-issue labels Apr 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/documentation good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. kind/support Categorizes issue or PR as a support question.
Projects
None yet
Milestone
1.5.1
Development

No branches or pull requests
5 participants
@justinsb @jonchiu @chrislovecnm @rifelpet @AndresPineros