Kops: Private topology with kubenet networking

Created on 4 Jan 2017 · 5Comments · Source: kubernetes/kops

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!

aredocumentation good first issue kinsupport

Source

jonchiu

Most helpful comment

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

justinsb on 4 Jan 2017

👍5

All 5 comments

@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?

chrislovecnm on 4 Jan 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

justinsb on 4 Jan 2017

👍5

@jonchiu would love you to document the above!

chrislovecnm on 4 Jan 2017

Closing

chrislovecnm on 16 Jul 2017

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