kubernetes
/
kops
mirror of https://github.com/kubernetes/kops.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Improve formatting of run_in_existing_vpc.md

This commit is contained in:
Thomas Peitz 2017-12-20 22:48:29 +01:00
parent 91fc6a83ba
commit 1eb1fdf163
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/run_in_existing_vpc.md
View File

@ -63,7 +63,7 @@ will be removed automatically if you delete your kops cluster.
- "kubernetes.io/cluster/<cluster-name>" = "shared"
```
Prior to kops 1.8 this Tag Key was KubernetesCluster which is obsolete and should
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.
@ -145,8 +145,8 @@ kops update cluster ${CLUSTER_NAME} --yes
If you run in AWS private topology with shared subnets, and you would like Kubernetes to provision resources in these shared subnets, you must create tags on them.
This is important, for example, if your `utility` subnets are shared, you will not be able to launch any services that create Elastic Load Balancers (ELBs).
Prior to kops 1.8 KubernetesCluster tag was used for this. This lead to several problems if there were more than one Kubernetes Cluster in a subnet.
After you upgraded to kops 1.8 remove KubernetesCluster Tag from Subnets as it is prioritized against "kubernetes.io/cluster/<clustername>"
Prior to kops 1.8 `KubernetesCluster` tag was used for this. This lead to several problems if there were more than one Kubernetes Cluster in a subnet.
After you upgraded to kops 1.8 remove `KubernetesCluster` Tag from Subnets as it is prioritized against `kubernetes.io/cluster/<clustername>`.
These are currently needed Tags on shared resources: