News for hackers. Stuff that matters.
Re:Kubernetes V1 Released by ghshephard on Tuesday July 21, 2015 @09:39AM (#9922144)
Add to that, how does this relate to Docker-Swarm & Core-OS Fleet.

StackOverflow has at least one quick briefer, but wow, this field is growing quickly:

http://stackoverflow.com/questions/27640633/docker-swarm-kub...

Re:Kubernetes V1 Released by waffle_ss on Tuesday July 21, 2015 @10:36AM (#9922524)
A couple things I've found when evaluating these:

Docker Swarm seems to be the only one that supports one-off interactive containers that bind a TTY, like a Rails console (i.e. does the cluster support `docker run -it --rm busybox sh`). But its scheduling strategies[1] aren't as sophisticated as the others.

Marathon doesn't support linked containers[2], so if you're using Mesos and need linked containers, you probably will want to run Kubernetes on it and use pods.

[1]: https://github.com/docker/swarm/tree/b2182d080956040730cc76c...

[2]: https://support.mesosphere.com/hc/en-us/articles/205006415-H...

Re:Kubernetes V1 Released by TheIronYuppie on Tuesday July 21, 2015 @01:35PM (#9924089)
Kubernetes does this as well:

cluster/kubectl.sh exec pod_name -ti bash

Full disclosure: I work at Google on Kubernetes

Re:Kubernetes V1 Released by waffle_ss on Tuesday July 21, 2015 @02:24PM (#9924544)
Awesome, good to know. Based on this issue[1] I didn't think it did.

[1]: https://github.com/GoogleCloudPlatform/kubernetes/issues/152...

Re:Kubernetes V1 Released by throwaway1979 on Tuesday July 21, 2015 @10:48AM (#9922603)
I've been playing with Swarm and like what I've seen so far. WRT Kubernetes, on a platform other than GCE, is Flannel required for networking?
Re:Kubernetes V1 Released by TheIronYuppie on Tuesday July 21, 2015 @01:37PM (#9924106)
Networking on AWS works fine with no additional networking as well.

Overlay networking is not required if you're running within a bunch of nodes that can see each other. Only if you get more complex will you require something, and there are quite a few solutions (Flannel, Weave, Calico, etc)

Full disclosure: I work at Google on Kubernetes

Re:Kubernetes V1 Released by merb on Tuesday July 21, 2015 @03:54PM (#9925263)
But most of them suck, and they suck even more when you configured them badly (badly in terms of you used an option which comes by default). However with the bigger vxlan adoption most performance issues are fixed, still, could have some improvmenents. I also think that IPv6 could fix a lot of these things...
Re:Kubernetes V1 Released by roque on Wednesday July 22, 2015 @12:08AM (#9927683)
As others have mentioned there are multiple options. If you want micro-segmentation (one network per app-tier) with fine-grain access control you can use the OpenContrail plugin https://github.com/Juniper/contrail-kubernetes. It has the added advantage that you have a tenant network span k8s, openstack, vlans, or anything else you can plug into a reasonable mid-tier router.

[Disclosure: i'm currently working on this project]

Re:Kubernetes V1 Released by amouat on Tuesday July 21, 2015 @11:26AM (#9922876)
I think you just need to provide a flat networking infrastructure where all nodes get their own IP and can reach each other. So you can swap flannel for project calico or your own setup if you like.
Re:Kubernetes V1 Released by eepyaich on Tuesday July 21, 2015 @11:39AM (#9922979)
Yep - see http://www.projectcalico.org/calico-networking-for-kubernete....

[Disclosure - I'm part of the Project Calico team.]

Re:Kubernetes V1 Released by dward on Tuesday July 21, 2015 @11:40AM (#9922983)
Weave and Openvswitch are two other options. Many IaaS (gcp, aws) provide the required nobs and dials to configure this "natively" using their API so no extra SDN required if you are already running on a compatible cloud provider.
Re:Kubernetes V1 Released by throwaway1979 on Tuesday July 21, 2015 @01:09PM (#9923820)
I thought each host needs an entire /24 subnet, and the pods that run on the host get individual IP addresses. Am I mistaken?
Re:Kubernetes V1 Released by TheIronYuppie on Tuesday July 21, 2015 @01:38PM (#9924117)
No, there's a private network that's shared between all the containers running on the pods, but as long as the nodes can see each other, you're good.

Full disclosure: I work at Google on Kubernetes