Difficulty: beginner
Estimated Time: 10-15 minutes

This scenario explains the different aspects of launching a Kubernetes cluster.

The environment has a Docker installation configured, running on a host called docker. Everything else required we'll launch as containers.

More information can be found at http://kubernetes.io/docs/getting-started-guides/

This scenario has explained how to launch a Kubernetes cluster. In future scenarios you'll learn more details about Kubernetes, starting with launching your first example application.

Let everyone know about your success:

Don’t stop now! The next scenario will take about 20 minutes to complete. You can pause and come back at any time.

Launch Single Node Kubernetes Cluster on CoreOS

Step 1 of 10

Step 1 - Etcd

Etcd is a "Distributed reliable key-value store for the most critical data of a distributed system". Kubernetes uses Etcd to store state about the cluster and service discovery between nodes. This state includes what nodes exist in the cluster, which nodes they are running on and what containers should be running.

CoreOS includes an Etcd2 deployment. You can check it's running using etcdctl cluster-health

To deploy you need to create a systemd configuration file, similar to the one used by cat /usr/lib64/systemd/system/etcd2.service

The binary can be downloaded from https://github.com/coreos/etcd/releases

In production you would want to run etcd on three separate machines to ensure maximum availability.