diff --git a/examples/node-selection/README.md b/examples/node-selection/README.md
index 826d0cf31ed..f22d624c2a5 100644
--- a/examples/node-selection/README.md
+++ b/examples/node-selection/README.md
@@ -23,37 +23,34 @@ You can verify that it worked by re-running `kubectl get nodes` and checking tha
 Take whatever pod config file you want to run, and add a nodeSelector section to it, like this. For example, if this is my pod config:
 
 <pre>
-apiVersion: v1beta1
-desiredState:
-  manifest:
-    containers:
-      - image: nginx
-        name: nginx
-    id: nginx
-    version: v1beta1
-id: nginx
+apiVersion: v1beta3
 kind: Pod
-labels:
-  env: test
+metadata:
+  labels:
+    env: test
+  name: nginx
+spec:
+  containers:
+  - image: nginx
+    name: nginx
 </pre>
 
 Then add a nodeSelector like so:
 
 <pre>
-apiVersion: v1beta1
-desiredState:
-  manifest:
-    containers:
-      - image: nginx
-        name: nginx
-    id: nginx
-    version: v1beta1
-id: nginx
+apiVersion: v1beta3
 kind: Pod
-labels:
-  env: test
-<b>nodeSelector:
-  disktype: ssd</b>
+metadata:
+  labels:
+    env: test
+  name: nginx
+spec:
+  containers:
+  - image: nginx
+    imagePullPolicy: IfNotPresent
+    name: nginx
+  <b>nodeSelector:
+    disktype: ssd</b>
 </pre>
 
 When you then run `kubectl create -f pod.yaml`, the pod will get scheduled on the node that you attached the label to! You can verify that it worked by running `kubectl get pods` and looking at the "host" that the pod was assigned to.
diff --git a/examples/node-selection/pod.yaml b/examples/node-selection/pod.yaml
new file mode 100644
index 00000000000..42a6b39e8a2
--- /dev/null
+++ b/examples/node-selection/pod.yaml
@@ -0,0 +1,13 @@
+apiVersion: v1beta3
+kind: Pod
+metadata:
+  labels:
+    env: test
+  name: nginx
+spec:
+  containers:
+  - image: nginx
+    imagePullPolicy: IfNotPresent
+    name: nginx
+  nodeSelector:
+    disktype: ssd