Point to the latest kubernetes documentation

doc/GettingStartedKubernetes.md

@@ -188,7 +188,7 @@ $ export KUBECTL=/example/path/to/google-cloud-sdk/bin/kubectl
     For other platforms, you'll need to choose the `file` backup storage plugin,
     and mount a read-write network volume into the `vttablet` and `vtctld` pods.
     For example, you can mount any storage service accessible through NFS into a
-    [Kubernetes volume](http://kubernetes.io/v1.0/docs/user-guide/volumes.html#nfs).
+    [Kubernetes volume](http://kubernetes.io/v1.1/docs/user-guide/volumes.html#nfs).
     Then provide the mount path to the configure script here.
 
     Direct support for other cloud blob stores like Amazon S3 can be added by
@@ -222,7 +222,7 @@ $ export KUBECTL=/example/path/to/google-cloud-sdk/bin/kubectl
     and the other is for a
     [local cell](http://vitess.io/overview/concepts.html#cell-data-center)
     called *test*. You can check the status of the
-    [pods](http://kubernetes.io/v1.0/docs/user-guide/pods.html)
+    [pods](http://kubernetes.io/v1.1/docs/user-guide/pods.html)
     in the cluster by running:
 
     ``` sh
@@ -269,7 +269,7 @@ $ export KUBECTL=/example/path/to/google-cloud-sdk/bin/kubectl
 1.  **Access vtctld web UI**
 
     To access vtctld from outside Kubernetes, use [kubectl proxy]
-    (http://kubernetes.io/v1.0/docs/user-guide/kubectl/kubectl_proxy.html)
+    (http://kubernetes.io/v1.1/docs/user-guide/kubectl/kubectl_proxy.html)
     to create an authenticated tunnel on your workstation:
 
     **Note:** The proxy command runs in the foreground,
@@ -286,7 +286,7 @@ $ export KUBECTL=/example/path/to/google-cloud-sdk/bin/kubectl
     http://localhost:8001/api/v1/proxy/namespaces/default/services/vtctld:web/
 
     You can also use this proxy to access the [Kubernetes Dashboard]
-    (http://kubernetes.io/v1.0/docs/user-guide/ui.html),
+    (http://kubernetes.io/v1.1/docs/user-guide/ui.html),
     where you can monitor nodes, pods, and services:
 
     http://localhost:8001/api/v1/proxy/namespaces/kube-system/services/kube-ui/
@@ -299,7 +299,7 @@ $ export KUBECTL=/example/path/to/google-cloud-sdk/bin/kubectl
     To enable RPC access into the Kubernetes cluster, we'll again use
     `kubectl` to set up an authenticated tunnel. Unlike the HTTP proxy
     we used for the web UI, this time we need raw [port forwarding]
-    (http://kubernetes.io/v1.0/docs/user-guide/kubectl/kubectl_port-forward.html)
+    (http://kubernetes.io/v1.1/docs/user-guide/kubectl/kubectl_port-forward.html)
     for vtctld's [gRPC](http://grpc.io) port.
 
     Since the tunnel needs to target a particular vtctld pod name,
@@ -336,7 +336,7 @@ $ export KUBECTL=/example/path/to/google-cloud-sdk/bin/kubectl
     `vttablet` and `mysqld` processes, running on the same
     host. We enforce this coupling in Kubernetes by putting the respective
     containers for vttablet and mysqld inside a single
-    [pod](http://kubernetes.io/v1.0/docs/user-guide/pods.html).
+    [pod](http://kubernetes.io/v1.1/docs/user-guide/pods.html).
 
     Run the following script to launch the vttablet pods, which also include
     mysqld:
@@ -503,7 +503,7 @@ $ export KUBECTL=/example/path/to/google-cloud-sdk/bin/kubectl
     query to the correct `vttablet`. In Kubernetes, a `vtgate` service
     distributes connections to a pool of `vtgate` pods. The pods are curated by
     a [replication controller]
-    (http://kubernetes.io/v1.0/docs/user-guide/replication-controller.html).
+    (http://kubernetes.io/v1.1/docs/user-guide/replication-controller.html).
 
     ``` sh
     vitess/examples/kubernetes$ ./vtgate-up.sh
@@ -536,11 +536,11 @@ As with the `vtctld` service, by default the GuestBook app is not accessible
 from outside Kubernetes. In this case, since this is a user-facing frontend,
 we set `type: LoadBalancer` in the GuestBook service definition,
 which tells Kubernetes to create a public
-[load balancer](http://kubernetes.io/v1.0/docs/user-guide/services.html#type-loadbalancer)
+[load balancer](http://kubernetes.io/v1.1/docs/user-guide/services.html#type-loadbalancer)
 using the API for whatever platform your Kubernetes cluster is in.
 
 You also need to [allow access through your platform's firewall]
-(http://kubernetes.io/v1.0/docs/user-guide/services-firewalls.html).
+(http://kubernetes.io/v1.1/docs/user-guide/services-firewalls.html).
 
 ``` sh
 # For example, to open port 80 in the GCE firewall: