From 631c5e485b3f1c6cb05095d311e45e2b835aea3e Mon Sep 17 00:00:00 2001 From: Marty Hernandez Avedon Date: Fri, 17 Nov 2023 10:19:19 -0500 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Billy Tat --- .../set-up-cloud-providers/amazon.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-cloud-providers/amazon.md b/docs/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-cloud-providers/amazon.md index 9e15a67c1db..10700b418d4 100644 --- a/docs/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-cloud-providers/amazon.md +++ b/docs/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-cloud-providers/amazon.md @@ -159,7 +159,7 @@ If you share resources between clusters, you can change the tag to: **Key** = `kubernetes.io/cluster/` **Value** = `shared`. -The string value, ``, should be the Kubernetes cluster's ID. Technically, the `` value can be any string you like, as long as you use the same value across all tags set. In practice, if the `ClusterID` is automatically configured for some nodes, as it is with Amazon EC2 nodes, you should consistently use that same string across all of your resources, even if you have to manually set the tag. +The string value, ``, is the Kubernetes cluster's ID. ### Using Amazon Elastic Container Registry (ECR)