Removed non-md files from docs. Moved doc yamls to test/fixtures.

Most of the contents of docs/ has moved to kubernetes.github.io.
Development of the docs and accompanying files has continued there, making
the copies in this repo stale. I've removed everything but the .md files
which remain to redirect old links. The .yaml config files in the docs
were used by some tests, these have been moved to test/fixtures/doc-yaml,
and can remain there to be used by tests or other purposes.

docs/user-guide/walkthrough/pod-nginx-with-label.yaml

@@ -1,12 +0,0 @@
-apiVersion: v1
-kind: Pod
-metadata:
-  name: nginx
-  labels:
-    app: nginx
-spec:
-  containers:
-  - name: nginx
-    image: nginx
-    ports:
-    - containerPort: 80

docs/user-guide/walkthrough/pod-nginx.yaml

@@ -1,10 +0,0 @@
-apiVersion: v1
-kind: Pod
-metadata:
-  name: nginx
-spec:
-  containers:
-  - name: nginx
-    image: nginx
-    ports:
-    - containerPort: 80

docs/user-guide/walkthrough/pod-redis.yaml

@@ -1,14 +0,0 @@
-apiVersion: v1
-kind: Pod
-metadata:
-  name: redis
-spec:
-  containers:
-  - name: redis
-    image: redis
-    volumeMounts:
-    - name: redis-persistent-storage
-      mountPath: /data/redis
-  volumes:
-  - name: redis-persistent-storage
-    emptyDir: {}

docs/user-guide/walkthrough/pod-with-http-healthcheck.yaml

@@ -1,20 +0,0 @@
-apiVersion: v1
-kind: Pod
-metadata:
-  name: pod-with-healthcheck
-spec:
-  containers:
-  - name: nginx
-    image: nginx
-    # defines the health checking
-    livenessProbe:
-      # an http probe
-      httpGet:
-        path: /_status/healthz
-        port: 80
-      # length of time to wait for a pod to initialize
-      # after pod startup, before applying health checking
-      initialDelaySeconds: 30
-      timeoutSeconds: 1
-    ports:
-    - containerPort: 80

docs/user-guide/walkthrough/podtemplate.json

@@ -1,22 +0,0 @@
-  {
-    "apiVersion": "v1",
-    "kind": "PodTemplate",
-    "metadata": {
-      "name": "nginx"
-    },
-    "template": {
-      "metadata": {
-        "labels": {
-          "name": "nginx"
-        },
-        "generateName": "nginx-"
-      },
-      "spec": {
-         "containers": [{
-           "name": "nginx",
-           "image": "dockerfile/nginx",
-           "ports": [{"containerPort": 80}]
-         }]
-      }
-    }
-  }

docs/user-guide/walkthrough/replication-controller.yaml

@@ -1,24 +0,0 @@
-apiVersion: v1
-kind: ReplicationController
-metadata:
-  name: nginx-controller
-spec:
-  replicas: 2
-  # selector identifies the set of Pods that this
-  # replication controller is responsible for managing
-  selector:
-    app: nginx
-  # podTemplate defines the 'cookie cutter' used for creating
-  # new pods when necessary
-  template:
-    metadata:
-      labels:
-        # Important: these labels need to match the selector above
-        # The api server enforces this constraint.
-        app: nginx
-    spec:
-      containers:
-      - name: nginx
-        image: nginx
-        ports:
-        - containerPort: 80

docs/user-guide/walkthrough/service.yaml

@@ -1,16 +0,0 @@
-apiVersion: v1
-kind: Service
-metadata:
-  name: nginx-service
-spec:
-  ports:
-  - port: 8000 # the port that this service should serve on
-    # the container on each pod to connect to, can be a name
-    # (e.g. 'www') or a number (e.g. 80)
-    targetPort: 80
-    protocol: TCP
-  # just like the selector in the replication controller,
-  # but this time it identifies the set of pods to load balance
-  # traffic to.
-  selector:
-    app: nginx