This project combines concepts and technologies from two already-complex projects: Mesos and Kubernetes. It may help to familiarize yourself with the basics of each project before reading on:
It may also be helpful to understand the known issues with respect to this project.
A Mesos cluster consists of one or more masters, and one or more slaves. Kubernetes-Mesos (k8sm) operates as a Mesos framework that runs on the cluster. As a framework, k8sm provides scheduler and executor components, both of which are hybrids of Kubernetes and Mesos: the scheduler component integrates the Kubernetes scheduling API and the Mesos scheduler runtime, whereas; the executor component integrates Kubernetes kubelet services and the Mesos executor runtime.
Multiple Mesos masters are typically configured to coordinate leadership election via Zookeeper.
Future releases of Mesos may implement leader election protocols differently.
Kubernetes maintains its internal registry (pods, replication controllers, bindings, minions, services) in etcd.
Users typically interact with Kubernetes using the kubecfg or kubectl commands to manage Kubernetes primitives.
When a pod is created in Kubernetes, the k8sm scheduler creates an associated Task and queues it for scheduling. Upon pairing the pod/task with an acceptable resource offer, the scheduler binds the pod/task to the offer's slave. As a result of binding the pod/task is launched and delivered to an executor (an executor is created by the Mesos slave if one is not already running). The executor launches the pod/task, which registers the bound pod with the kubelet engine and the kubelet begins to manage the lifecycle of the pod instance.
Kubernetes-Mesos defaults to "normal" Docker IPv4, host-private networking. This allows services to operate, but creates other issues.
