Commit 06c96597 authored by Abhi Shah's avatar Abhi Shah

Merge pull request #9602 from krousey/example_walkthrough

Changing walkthrough to v1
parents ccb1b658 0cd638f2
......@@ -10,7 +10,7 @@ See [pods](../../docs/pods.md) for more details.
Trivially, a single container might be a pod. For example, you can express a simple web server as a pod:
```yaml
apiVersion: v1beta3
apiVersion: v1
kind: Pod
metadata:
name: www
......@@ -28,7 +28,7 @@ See the [design document](../../DESIGN.md) for more details.
Now that's great for a static web server, but what about persistent storage? We know that the container file system only lives as long as the container does, so we need more persistent storage. To do this, you also declare a ```volume``` as part of your pod, and mount it into a container:
```yaml
apiVersion: v1beta3
apiVersion: v1
kind: Pod
metadata:
name: storage
......@@ -77,7 +77,7 @@ The examples below are syntactically correct, but some of the images (e.g. kuber
However, often you want to have two different containers that work together. An example of this would be a web server, and a helper job that polls a git repository for new updates:
```yaml
apiVersion: v1beta3
apiVersion: v1
kind: Pod
metadata:
name: www
......
......@@ -22,7 +22,7 @@ Replication controllers are the objects to answer these questions. A replicatio
An example replication controller that instantiates two pods running nginx looks like:
```yaml
apiVersion: v1beta3
apiVersion: v1
kind: ReplicationController
metadata:
name: nginx-controller
......@@ -53,7 +53,7 @@ Once you have a replicated set of pods, you need an abstraction that enables con
For example, here is a service that balances across the pods created in the previous nginx replication controller example:
```yaml
apiVersion: v1beta3
apiVersion: v1
kind: Service
metadata:
name: nginx-example
......@@ -125,7 +125,7 @@ The container health checks are configured in the "LivenessProbe" section of you
Here is an example config for a pod with an HTTP health check:
```yaml
apiVersion: v1beta3
apiVersion: v1
kind: Pod
metadata:
name: pod-with-healthcheck
......
apiVersion: v1beta3
apiVersion: v1
kind: Pod
metadata:
name: pod-with-healthcheck
......
apiVersion: v1beta3
apiVersion: v1
kind: Pod
metadata:
name: www
......
apiVersion: v1beta3
apiVersion: v1
kind: Pod
metadata:
name: storage
......
{
"apiVersion": "v1beta3",
"apiVersion": "v1",
"kind": "PodTemplate",
"metadata": {
"name": "nginx"
......
apiVersion: v1beta3
apiVersion: v1
kind: ReplicationController
metadata:
name: nginx-controller
......
apiVersion: v1beta3
apiVersion: v1
kind: Service
metadata:
name: nginx-example
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment