diff --git a/docs/run_in_existing_vpc.md b/docs/run_in_existing_vpc.md
index c0137ff13d..6ef5d7a072 100644
--- a/docs/run_in_existing_vpc.md
+++ b/docs/run_in_existing_vpc.md
@@ -57,11 +57,14 @@ Once you're happy, you can create the cluster using:
 kops update cluster ${CLUSTER_NAME} --yes
 ```
 
+This will add an additional Tag to your aws vpc resource. This tag
+will be removed automatically if you delete your kops cluster.
+```
+- "kubernetes.io/cluster/<cluster-name>" = "shared"
+```
 
-Finally, if your shared VPC has a KubernetesCluster tag (because it was created with kops), you should
-probably remove that tag to indicate that the resources are not owned by that cluster, and so
-deleting the cluster won't try to delete the VPC.  (Deleting the VPC won't succeed anyway, because it's in use,
-but it's better to avoid the later confusion!)
+Prior to kops 1.8 this Tag Key was KubernetesCluster which is obsolete and should
+not be used anymore as it only supports one cluster.
 
 
 ### VPC with multiple CIDRs
@@ -159,11 +162,6 @@ Private Subnets:
 - "kubernetes.io/role/internal-elb"         = "1"
 ```
 
-VPC:
-```
-- "kubernetes.io/cluster/<cluster-name>" = "shared"
-```
-
 
 ### Shared NAT Gateways