networking - Running Kubernetes on vCenter -
so kubernetes has pretty novel network model, believe based on perceives shortcoming default docker networking. while i'm still struggling understand: (1) perceives actual shortcoming(s) be, , (2) kubernetes' general solution is, i'm reaching point i'd implement solution , perhaps clue me in little better.
whereas rest of kubernetes documentation mature , well-written, instructions configuring network sparse, largely incoherent, , span many disparate articles, instead of being located in 1 particular place.
i'm hoping has set kubernetes cluster before (from scratch) can walk me through basic procedures. i'm not interested in running on gce or aws, , i'm not interested in using kind of overlay network flannel.
my basic understanding is:
- carve out
/16subnet pods. limit 65k pods, should sufficient normal applications. ips in subnet must "public" , not inside of traditionally-private (classful) range. - create
cbr0bridge somewhere , make sure persistent (but on machine?) - remove/disable
masqueraderule installed docker. - some how configure
iptablesroutes (again, where?) each pod spun kubernetes receives 1 of public ips. - some other setup required make use of load balanced
services, dynamic dns. - provision 5 vms: 1 master, 4 minions
- install/configure docker on 5 vms
- install/configure
kubectl,controller-manager,apiserver,etcdmaster, , run them services/daemons - install/configure
kubelet,kube-proxyon each minion , run them services/daemons
this best can collect 2 full days of research, , wrong (or misdirected), out of order, , utterly incomplete.
i have unbridled access create vms in on-premise vcenter cluster. if changes need made vlan/switches/etc. can infrastructure involved.
how many vms should set kubernetes (for small-to-medium sized cluster), , why? exact corrections need make vague instructions above, networking totally configured?
i'm installing/configuring binaries. totally choking on network side of setup.
for general introduction kubernetes networking, found http://www.slideshare.net/enakai/architecture-overview-kubernetes-with-red-hat-enterprise-linux-71 pretty helpful.
on items (1) , (2): imho nicely described in https://github.com/kubernetes/kubernetes/blob/master/docs/admin/networking.md#docker-model . experience: problem docker nat type of approach? need configure e.g. software endpoints of nodes (172.168.10.1:8080, 172.168.10.2:8080, etc). in kubernetes can configure ip's of pods each others pod, docker complicates using nat indirection. see setting network kubernetes nice answer.
comments on other points: 1.
all ips in subnet must "public" , not inside of traditionally-private (classful) range.
the "internal network" of kubernetes uses private ip's, see slides above, uses 10.x.x.x example. guess confusion comes kubernetes texts refer "public" "visible outside of node", not mean "internet public ip address range".
Comments
Post a Comment