Import from Container Engine docs, addition of Tabs functionality, various link fixes

docs/user-guide/pods/single-container.md

@@ -0,0 +1,88 @@
+---
+---
+
+* TOC
+{:toc}
+
+A pod is a group of containers that are scheduled
+onto the same host. Pods serve as units of scheduling, deployment, and
+horizontal scaling/replication. Pods share fate, and share some resources, such
+as storage volumes and IP addresses.
+
+## Creating a pod
+
+Single-container pods can be created with the `run` command. The
+pod's properties are specified with flags on the command line.
+
+The `run` command creates a replication controller to monitor the pod(s).
+The controller watches for failed pods and will start up new pods as required
+to maintain the specified number.
+
+Note: If you don't want a replication controller to monitor your pod (e.g. your pod
+is writing non-persistent data which won't survive a restart, or your pod is
+intended to be very short-lived), you can
+[create a pod directly with the `create` command](/docs/user-guide/pods/multi-container/).
+
+To create a pod using the `run` command:
+
+```shell
+$ kubectl run NAME
+    --image=image
+    [--port=port]
+    [--replicas=replicas]
+    [--labels=key=value,key=value,...]
+```
+
+Where:
+
+* `NAME` (required) is the name of the container to create. This value is also
+  applied as the name of the replication controller, and as the prefix of the
+  pod name. For example:
+  
+  ```shell 
+  $ kubectl run example --image=nginx
+  replicationcontroller "example" created
+
+  $ kubectl get pods
+  NAME                 READY     STATUS    RESTARTS   AGE
+  example-xypvc        1/1       Running   0          13s
+  ```
+* `--image=IMAGE` (required) is the Docker container image to use for this
+   container.
+* `--port=PORT` is the port to expose on the container.
+* `--replicas=NUM` is the number of replicated pods to create. If not specified,
+  one pod will be created.
+* `--labels=key=value` specifies one or more labels to attach to the pod. In
+  addition to any labels specified here, `run` attaches a label of
+  the format `run=NAME`. This is used by the replication controller
+  to target the pods created by the command.
+
+There are additional flags that can be specified. For a complete list, run:
+
+    $ kubectl run --help
+
+## Viewing a pod
+
+{% include_relative _viewing-a-pod.md %}
+
+## Deleting a pod
+
+If your pod was created using the `run` command, kubernetes creates a
+[replication controller](/docs/user-guide/replication-controller/)
+to manage the pod. Pods managed by a replication controller are rescheduled if
+they go away, including being deleted by `kubectl delete pod`. To permanently
+delete the pod, delete its replication controller.
+
+First, find the controller's name:
+
+```shell
+$ kubectl get rc
+CONTROLLER  CONTAINER(S)  IMAGE(S)  SELECTOR     REPLICAS
+example     example       busybox   run=example  1
+```
+
+Then, `delete` the controller:
+
+```shell
+$ kubectl delete rc CONTROLLER_NAME
+```