Updating docs/ to v1

docs/design/expansion.md

@@ -348,7 +348,7 @@ No other variables are defined.
 Notice the `$(var)` syntax.
 
 ```yaml
-apiVersion: v1beta3
+apiVersion: v1
 kind: Pod
 metadata:
   name: expansion-pod
@@ -366,7 +366,7 @@ spec:
 #### In a pod: building a URL using downward API
 
 ```yaml
-apiVersion: v1beta3
+apiVersion: v1
 kind: Pod
 metadata:
   name: expansion-pod

docs/design/namespaces.md

@@ -231,7 +231,7 @@ OpenShift creates a Namespace in Kubernetes
 
 ```
 {
-  "apiVersion":"v1beta3",
+  "apiVersion":"v1",
   "kind": "Namespace",
   "metadata": {
     "name": "development",
@@ -256,7 +256,7 @@ User deletes the Namespace in Kubernetes, and Namespace now has following state:
 
 ```
 {
-  "apiVersion":"v1beta3",
+  "apiVersion":"v1",
   "kind": "Namespace",
   "metadata": {
     "name": "development",
@@ -281,7 +281,7 @@ removing *kubernetes* from the list of finalizers:
 
 ```
 {
-  "apiVersion":"v1beta3",
+  "apiVersion":"v1",
   "kind": "Namespace",
   "metadata": {
     "name": "development",
@@ -309,7 +309,7 @@ This results in the following state:
 
 ```
 {
-  "apiVersion":"v1beta3",
+  "apiVersion":"v1",
   "kind": "Namespace",
   "metadata": {
     "name": "development",

docs/design/persistent-storage.md

@@ -98,7 +98,7 @@ An administrator provisions storage by posting PVs to the API.  Various way to a
 POST:
 
 kind: PersistentVolume
-apiVersion: v1beta3
+apiVersion: v1
 metadata:
   name: pv0001
 spec:
@@ -128,7 +128,7 @@ The user must be within a namespace to create PVCs.
 
 POST: 
 kind: PersistentVolumeClaim
-apiVersion: v1beta3
+apiVersion: v1
 metadata:
   name: myclaim-1
 spec:
@@ -179,7 +179,7 @@ The claim holder owns the claim and its data for as long as the claim exists.  T
 POST: 
 
 kind: Pod
-apiVersion: v1beta3
+apiVersion: v1
 metadata:
   name: mypod
 spec:

docs/design/secrets.md

@@ -394,7 +394,7 @@ To create a pod that uses an ssh key stored as a secret, we first need to create
 ```json
 {
   "kind": "Secret",
-  "apiVersion": "v1beta3",
+  "apiVersion": "v1",
   "metadata": {
     "name": "ssh-key-secret"
   },
@@ -414,7 +414,7 @@ Now we can create a pod which references the secret with the ssh key and consume
 ```json
 {
   "kind": "Pod",
-  "apiVersion": "v1beta3",
+  "apiVersion": "v1",
   "metadata": {
     "name": "secret-test-pod",
     "labels": {
@@ -464,12 +464,12 @@ The secrets:
 
 ```json
 {
-  "apiVersion": "v1beta3",
+  "apiVersion": "v1",
   "kind": "List",
   "items":
   [{
     "kind": "Secret",
-    "apiVersion": "v1beta3",
+    "apiVersion": "v1",
     "metadata": {
       "name": "prod-db-secret"
     },
@@ -480,7 +480,7 @@ The secrets:
   },
   {
     "kind": "Secret",
-    "apiVersion": "v1beta3",
+    "apiVersion": "v1",
     "metadata": {
       "name": "test-db-secret"
     },
@@ -496,12 +496,12 @@ The pods:
 
 ```json
 {
-  "apiVersion": "v1beta3",
+  "apiVersion": "v1",
   "kind": "List",
   "items":
   [{
     "kind": "Pod",
-    "apiVersion": "v1beta3",
+    "apiVersion": "v1",
     "metadata": {
       "name": "prod-db-client-pod",
       "labels": {
@@ -534,7 +534,7 @@ The pods:
   },
   {
     "kind": "Pod",
-    "apiVersion": "v1beta3",
+    "apiVersion": "v1",
     "metadata": {
       "name": "test-db-client-pod",
       "labels": {