From 7afd4ef71bda9fbac16ce2e26382cdc88227c990 Mon Sep 17 00:00:00 2001 From: MikeJeffrey Date: Wed, 19 Nov 2014 15:45:30 -0800 Subject: [PATCH] Rolling back apiVersion change --- examples/walkthrough/README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/examples/walkthrough/README.md b/examples/walkthrough/README.md index 267e653cf64..c7454e88acc 100644 --- a/examples/walkthrough/README.md +++ b/examples/walkthrough/README.md @@ -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 -version: v1beta1 +apiVersion: v1beta1 id: www desiredState: manifest: @@ -30,7 +30,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 -version: v1beta1 +apiVersion: v1beta1 id: storage desiredState: manifest: @@ -87,7 +87,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 -version: v1beta1 +apiVersion: v1beta1 id: www desiredState: manifest: