Syntax highlighting

2016-02-16 17:53:42 -08:00
parent bbeb111863
commit ee72211075
115 changed files with 1922 additions and 1919 deletions
@@ -85,9 +85,9 @@ a simple cluster set up, using etcd's built in discovery to build our cluster.

 First, hit the etcd discovery service to create a new token:

-{% highlight sh %}
+```shell

-curl https://discovery.etcd.io/new?size=3
+curl https://discovery.etcd.io/new?size=3

 ```

@@ -103,15 +103,15 @@ for `${NODE_IP}` on each machine.

 #### Validating your cluster

-Once you copy this into all three nodes, you should have a clustered etcd set up.  You can validate with
+Once you copy this into all three nodes, you should have a clustered etcd set up.  You can validate with

-{% highlight sh %}
+```shell

 etcdctl member list

-{% endhighlight %}
+```

-and
+and

 ```shell

@@ -141,9 +141,9 @@ Once you have replicated etcd set up correctly, we will also install the apiserv

 ## Replicated API Servers

-Once you have replicated etcd set up correctly, we will also install the apiserver using the kubelet.
+Once you have replicated etcd set up correctly, we will also install the apiserver using the kubelet.

-### Installing configuration files
+### Installing configuration files

 First you need to create the initial log file, so that Docker mounts a file instead of a directory:

@@ -193,10 +193,10 @@ In the future, we expect to more tightly integrate this lease-locking into the s
 instances of these actors, in case a machine dies.  To achieve this, we are going to use a lease-lock in etcd to perform
 master election.  On each of the three apiserver nodes, we run a small utility application named `podmaster`. It's job is to implement a master
 election protocol using etcd "compare and swap". If the apiserver node wins the election, it starts the master component it is managing (e.g. the scheduler), if it
-loses the election, it ensures that any master components running on the node (e.g. the scheduler) are stopped.
+loses the election, it ensures that any master components running on the node (e.g. the scheduler) are stopped.

 In the future, we expect to more tightly integrate this lease-locking into the scheduler and controller-manager binaries directly, as described in the [high availability design proposal](../proposals/high-availability)
-
+
 ### Installing configuration files

 First, create empty log files on each node, so that Docker will mount the files not make new directories: