From fdc43efd6843a23dd61efdd0a597dac88c7f581e Mon Sep 17 00:00:00 2001
From: Brendan Burns <bburns@google.com>
Date: Mon, 24 Nov 2014 10:05:07 -0800
Subject: [PATCH] Update PD example.

---
 docs/volumes.md | 25 +++++++++++++++++++++++++
 1 file changed, 25 insertions(+)

diff --git a/docs/volumes.md b/docs/volumes.md
index 02172f7168e..07b196b71c3 100644
--- a/docs/volumes.md
+++ b/docs/volumes.md
@@ -50,3 +50,28 @@ There are some restrictions when using a GCEPersistentDisk:
   - avoid creating multiple pods that use the same Volume
     - if multiple pods refer to the same Volume and both are scheduled on the same machine, regardless of whether they are read-only or read-write, then the second pod scheduled will fail.
     - Replication controllers can only be created for pods that use read-only mounts.
+
+Example configuration:
+```yaml
+apiVersion: v1beta1
+desiredState:
+  manifest:
+    containers:
+      - image: kubernetes/pause
+        name: testpd
+        volumeMounts:
+          - mountPath: "/testpd"
+            name: "testpd"
+    id: testpd
+    version: v1beta1
+    volumes:
+      - name: testpd
+        source:
+          - persistentDisk:
+              # This GCE PD must already exist and be formatted ext4
+              pdName: test
+              fsType: ext4
+  id: testpd
+  kind: Pod
+  ```
+