54 Commits

Author	SHA1	Message	Date
Justin Santa Barbara	6f1341dd04	Add docker flags: insecure-registry and mtu ... Also add tests Issue #42	2016-08-08 13:55:34 -04:00
Justin Santa Barbara	2b3f55563e	Run the master on the pod network, unless IsolateMaster=true ... The master is now registered as a Node. It is marked as Unschedulable, so normal pods will not run on it. But Daemonsets will, and it is surprising that they don't work unless hostNetwork=true. The default is now what seems to be expected: * we allocate the master a real CIDR on the pod network * kube-proxy runs on the master, so it can talk to pods * we run kubelet on the master with enable-debugging-handlers, so kubectl logs etc works To get the old behaviour, edit the cluster spec and set `isolateMasters: true`	2016-07-28 12:12:16 -04:00
Justin Santa Barbara	1240e1d924	Fix bug where edit cluster was computing with the old spec ... Also add some tests, and fix some variable naming to hopefully stop it happening again. Fix #194	2016-07-22 18:19:40 -04:00
Justin Santa Barbara	31892fb08d	Refactor tests for cleaner separation	2016-07-22 10:19:01 -04:00