mentioned name_tag_prefix in README.md

Author: rberlind

infrastructure-as-code/k8s-cluster-openshift-aws/README.md

@@ -75,7 +75,7 @@ If you want to use open source Terraform instead of TFE, you can create a copy o
 1. Configure the workspace to connect to the fork of this repository in your own Github account.
 1. Set the Terraform Working Directory to "infrastructure-as-code/k8s-cluster-openshift-aws".
 1. On the Variables tab of your workspace, add the following variables to the Terraform variables: key_name, private_key_data, vault_addr, vault_user, and vault_k8s_auth_path. The first of these must be the name of the key pair you created above. The second must be the actual contents of the private key you downloaded as a pem file.  Be sure to mark this variable as sensitive so that it will not be visible after you save your variables. Set vault_addr to the address of your Vault server (e.g., "http://<your_vault_dns>:8200") and vault_user to your username on your Vault server. Finally, set vault_k8s_auth_path to something like "<your username>-openshift".
-1. HashiCorp SEs should also set the owner and ttl variables which are used by the AWS Lambda reaper function that terminates old EC2 instances.
+1. HashiCorp SEs should also set the owner and ttl variables which are used by the AWS Lambda reaper function that terminates old EC2 instances. To better distinguish AWS resources based on their Name tags, it is also advisable to set the name_tag_prefix variable to something like "\<your_name\> OpenShift".
 1. Set the VAULT_TOKEN environment variable to your Vault token. Be sure to mark the VAULT_TOKEN variable as sensitive so that other people cannot read it.
 
 ### Step 4: Provision Your OpenShift Cluster