move user docs to their new home

docs/user-guide/liveness/README.md

@@ -0,0 +1,88 @@
+<!-- BEGIN MUNGE: UNVERSIONED_WARNING -->
+
+<!-- BEGIN STRIP_FOR_RELEASE -->
+
+<h1>*** PLEASE NOTE: This document applies to the HEAD of the source
+tree only. If you are using a released version of Kubernetes, you almost
+certainly want the docs that go with that version.</h1>
+
+<strong>Documentation for specific releases can be found at
+[releases.k8s.io](http://releases.k8s.io).</strong>
+
+<!-- END STRIP_FOR_RELEASE -->
+
+<!-- END MUNGE: UNVERSIONED_WARNING -->
+## Overview
+This example shows two types of pod health checks: HTTP checks and container execution checks.
+
+The [exec-liveness.yaml](exec-liveness.yaml) demonstrates the container execution check.
+```
+    livenessProbe:
+      exec:
+        command:
+        - cat
+        - /tmp/health
+      initialDelaySeconds: 15
+      timeoutSeconds: 1
+```
+Kubelet executes the command cat /tmp/health in the container and reports failure if the command returns a non-zero exit code.
+
+Note that the container removes the /tmp/health file after 10 seconds,
+```
+echo ok > /tmp/health; sleep 10; rm -rf /tmp/health; sleep 600
+```
+so when Kubelet executes the health check 15 seconds (defined by initialDelaySeconds) after the container started, the check would fail.
+
+
+The [http-liveness.yaml](http-liveness.yaml) demonstrates the HTTP check.
+```
+    livenessProbe:
+      httpGet:
+        path: /healthz
+        port: 8080
+      initialDelaySeconds: 15
+      timeoutSeconds: 1
+```
+The Kubelet sends a HTTP request to the specified path and port to perform the health check. If you take a look at image/server.go, you will see the server starts to respond with an error code 500 after 10 seconds, so the check fails.
+
+This [guide](../walkthrough/k8s201.md#health-checking) has more information on health checks.
+
+## Get your hands dirty
+To show the health check is actually working, first create the pods:
+```
+# kubectl create -f exec-liveness.yaml
+# kubectl create -f http-liveness.yaml
+```
+
+Check the status of the pods once they are created:
+```
+# kubectl get pods
+NAME                                           READY     STATUS       RESTARTS   AGE
+[...]
+liveness-exec                                  1/1       Running      0          13s
+liveness-http                                  1/1       Running      0          13s
+```
+Check the status half a minute later, you will see the container restart count being incremented:
+```
+# kubectl get pods
+mwielgus@mwielgusd:~/test/k2/kubernetes/examples/liveness$ kubectl get pods
+NAME                                           READY     STATUS       RESTARTS   AGE
+[...]
+liveness-exec                                  1/1       Running      1          36s
+liveness-http                                  1/1       Running      1          36s
+```
+At the bottom of the *kubectl describe* output there are messages indicating that the liveness probes have failed, and the containers have been killed and recreated.
+
+```
+# kubectl describe pods liveness-exec
+[...]
+Sat, 27 Jun 2015 13:43:03 +0200    Sat, 27 Jun 2015 13:44:34 +0200    4    {kubelet kubernetes-minion-6fbi}    spec.containers{liveness}    unhealthy  Liveness probe failed: cat: can't open '/tmp/health': No such file or directory
+Sat, 27 Jun 2015 13:44:44 +0200    Sat, 27 Jun 2015 13:44:44 +0200    1    {kubelet kubernetes-minion-6fbi}    spec.containers{liveness}    killing    Killing with docker id 65b52d62c635
+Sat, 27 Jun 2015 13:44:44 +0200    Sat, 27 Jun 2015 13:44:44 +0200    1    {kubelet kubernetes-minion-6fbi}    spec.containers{liveness}    created    Created with docker id ed6bb004ee10
+Sat, 27 Jun 2015 13:44:44 +0200    Sat, 27 Jun 2015 13:44:44 +0200    1    {kubelet kubernetes-minion-6fbi}    spec.containers{liveness}    started    Started with docker id ed6bb004ee10
+```
+
+
+<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
+[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/liveness/README.md?pixel)]()
+<!-- END MUNGE: GENERATED_ANALYTICS -->

docs/user-guide/liveness/exec-liveness.yaml

@@ -0,0 +1,21 @@
+apiVersion: v1
+kind: Pod
+metadata:
+  labels:
+    test: liveness
+  name: liveness-exec
+spec:
+  containers:
+  - args:
+    - /bin/sh
+    - -c
+    - echo ok > /tmp/health; sleep 10; rm -rf /tmp/health; sleep 600
+    image: gcr.io/google_containers/busybox
+    livenessProbe:
+      exec:
+        command:
+        - cat
+        - /tmp/health
+      initialDelaySeconds: 15
+      timeoutSeconds: 1
+    name: liveness

docs/user-guide/liveness/http-liveness.yaml

@@ -0,0 +1,18 @@
+apiVersion: v1
+kind: Pod
+metadata:
+  labels:
+    test: liveness
+  name: liveness-http
+spec:
+  containers:
+  - args:
+    - /server
+    image: gcr.io/google_containers/liveness
+    livenessProbe:
+      httpGet:
+        path: /healthz
+        port: 8080
+      initialDelaySeconds: 15
+      timeoutSeconds: 1
+    name: liveness

docs/user-guide/liveness/image/Dockerfile

@@ -0,0 +1,4 @@
+FROM scratch
+
+ADD server /server
+

docs/user-guide/liveness/image/Makefile

@@ -0,0 +1,13 @@
+all: push
+
+server: server.go
+	CGO_ENABLED=0 GOOS=linux go build -a -installsuffix cgo -ldflags '-w' ./server.go
+
+container: server
+	docker build -t gcr.io/google_containers/liveness .
+
+push: container
+	gcloud docker push gcr.io/google_containers/liveness
+
+clean:
+	rm -f server

docs/user-guide/liveness/image/server.go

@@ -0,0 +1,46 @@
+/*
+Copyright 2014 The Kubernetes Authors All rights reserved.
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+*/
+
+// A simple server that is alive for 10 seconds, then reports unhealthy for
+// the rest of its (hopefully) short existence.
+package main
+
+import (
+	"fmt"
+	"log"
+	"net/http"
+	"time"
+)
+
+func main() {
+	started := time.Now()
+	http.HandleFunc("/started", func(w http.ResponseWriter, r *http.Request) {
+		w.WriteHeader(200)
+		data := (time.Now().Sub(started)).String()
+		w.Write([]byte(data))
+	})
+	http.HandleFunc("/healthz", func(w http.ResponseWriter, r *http.Request) {
+		duration := time.Now().Sub(started)
+		if duration.Seconds() > 10 {
+			w.WriteHeader(500)
+			w.Write([]byte(fmt.Sprintf("error: %v", duration.Seconds())))
+		} else {
+			w.WriteHeader(200)
+			w.Write([]byte("ok"))
+		}
+	})
+	log.Fatal(http.ListenAndServe(":8080", nil))
+}