brendandburns
State of the container world, March 2016
Scaling neural net image classification using Kubernetes with TensorFlow Serving
The central master handles node failures by removing nodes that aren't heartbeating.
On the node, we require a process monitor for the kubelet (by default we use supervisord) but then the kubelet monitors Docker [and also does garbage collection and resource limiting ], and then all of the other node daemons (e.g. the kubernetes proxy) are run/monitored/restarted by the kubelet.
Announcing Docker Cloud: One big failure.
State of the container world, February 2016
Goldman Sachs Switching to Kubernetes and Docker
Learn how ShareThis runs Kubernetes in production on AWS
I tried to describe this bias at the top of the blog post.
State of the container world, January 2016
Why Kubernetes isn't using Docker's libnetwork
Simple Leader Election with Kubernetes and Docker
Its great to see this launch. We've had flexible resources for container workloads for a while, its great to see them be available for more traditional VM workloads too!
Real life chaos monkey on a Raspberry Pi Kubernetes cluster
Kubernetes: Zero downtime update while handling one million req per sec
I'd recommend anyone trying to install Kubernetes check out: https://get.k8s.io/
Or the single node Docker based instructions:
https://github.com/kubernetes/kubernetes/blob/master/docs/ge...
Or boot2k8s: https://github.com/skippbox/boot2k8s
Or kubernetes on OS X: https://github.com/rimusz/coreos-osx-gui-kubernetes-cluster
Or of course the "as a service" versions like Google Container Engine, CoreOS Tectonic, etc.
We're definitely also working on simplifying the install instructions.
I'd also like to expand a little on some of the features that differentiate Swarm from Kuberentes, namely:
* Secrets
* Replicated sets of containers
* Rolling update from one version of code to the next
* AutoScaling (Kubernetes 1.1, in Release Candidate now)
* HTTP load balancing for autoscaling
* Load balancing for sets of objects (e.g. Frontend)
* Service discovery of those replicated sets (Swarm has discovery for individual containers, but no concept of Service)
In general, our goal is to build a system that makes distributed system construction easier.I would also refer people to the discussion in https://github.com/docker/compose/issues/1899#issuecomment-1... as well as https://github.com/docker/docker/pull/8859 on why we feel that the Node-based Docker API is problematic for a cluster level API.
Kubernetes as Foundation for Cloud Native PaaS
Kubernetes Performance Measurements and Roadmap
Kubernetes on Raspberry Pi
It is well supported on AWS as well, and a variety of bare-metal solutions (e.g. Red Hat Atomic, CoreOS)
However, concretely, it is a challenge to maintain good support for N different platforms without an owner who is willing to stand up and ensure that it works, and continues to work for that platform.
We have gotten a number of drive-by contributions of "how to" guides that (sadly) bit-rot over time. As always, we're working on improving the situation, but it is complicated and requires a great deal of time and access to infrastructure (e.g. Rackspace) that the core team simply doesn't have.
And ports are different between different replicas of your service, since they're chosen at random during scheduling.
It also makes ACLs and QoS harder to define for the network, since you don't have a clean network identity (e.g IP Address) for each application.
https://github.com/GoogleCloudPlatform/kubernetes/blob/maste...
which is designed to address some of this.
(as does every public cloud provider [e.g. AWS])
For now, VMs are required to ensure a security barrier between different user's containers on the same physical machine. See some of Dan Walsh's posts on the subject (e.g. https://opensource.com/business/14/9/security-for-docker) for more context.
SDN isn't required for k8s, what is required is that each Pod (group of containers) get it's own IP address, and that the IP address is routeable in the cluster. In many cases, the easiest way to achieve this is via an SDN, but it is also achievable by programming traditional routers.
The reason for wanting an IP address per pod is that it eliminates the need for port mangling, which dramatically simplifies wiring applications together.
https://github.com/GoogleCloudPlatform/kubernetes/blob/maste...
It's a fairly straightforward getting started experience.
Also, if you want to turn up a cluster in a cloud provider, it's as simple as https://get.k8s.io
Kubernetes is heavily inspired by both Borg and Omega, and incorporates many of the ideas from both, as well as lessons learned along the way. And many of the engineers who work on Kubernetes at Google, also worked on Omega and Borg.
for turn up instructions on AWS, it's as easy as:
export KUBERNETES_PROVIDER=aws; wget -q -O - https://get.k8s.io | bash
One of the reasons that I pushed hard to get Kubernetes open sourced, is the hope that we could get out in front of this, and allow the developer community to rally around Kubernetes as an open standard, independent of any provider or corporate agenda.