diff --git a/install_config/configuring_aws.adoc b/install_config/configuring_aws.adoc index ffdc1be22534..2a0ddf37711c 100644 --- a/install_config/configuring_aws.adoc +++ b/install_config/configuring_aws.adoc @@ -280,12 +280,14 @@ if you configured AWS provider credentials, you must also ensure that all hosts are labeled. To correctly identify which resources are associated with a cluster, tag -resources with the key `kubernetes.io/cluster/,Value=`, where: +resources with the key `kubernetes.io/cluster/`, where: -* `` is a unique name for the cluster. -* `` is a cluster identifier unique to the AWS Availability Zone. +* `` is a unique name for the cluster. -Tagging all relevant resources with the `kubernetes.io/cluster/,Value=` +Set the corresponding value to `owned` if the node belongs exclusively to the +cluster or to `shared` if it is a resource shared with other systems. + +Tagging all resources with the `kubernetes.io/cluster/,Value=(owned|shared)` tag avoids potential issues with multiple zones or multiple clusters. [NOTE] @@ -309,11 +311,11 @@ There are four types of resources that need to be tagged: [[aws-tagging-an-existing-cluster]] === Tagging an Existing Cluster -A cluster uses the value of the `kubernetes.io/cluster/,Value=` -tag to determine which resources belong to the AWS cluster. This means that all -relevant resources must be labeled with the -`kubernetes.io/cluster/,Value=` using the same values for that -key. These resources include: +A cluster uses the value of the +`kubernetes.io/cluster/,Value=(owned|shared)` tag to determine which +resources belong to the AWS cluster. This means that all relevant resources must +be labeled with the `kubernetes.io/cluster/,Value=(owned|shared)` +tag using the same values for that key. These resources include: * All hosts. * All relevant load balancers to be used in the AWS instances.