From 7450fa6f084e33d1da08551631ee195096bf3aad Mon Sep 17 00:00:00 2001 From: jaradtke-aws Date: Wed, 3 Jul 2024 09:44:59 -0400 Subject: [PATCH] Updating suggestion for Global Role name to align with other examples in doc --- .../en/docs/getting-started/vsphere/vsphere-preparation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/en/docs/getting-started/vsphere/vsphere-preparation.md b/docs/content/en/docs/getting-started/vsphere/vsphere-preparation.md index 0ce77aae5a54..78892e0295b4 100644 --- a/docs/content/en/docs/getting-started/vsphere/vsphere-preparation.md +++ b/docs/content/en/docs/getting-started/vsphere/vsphere-preparation.md @@ -161,7 +161,7 @@ So you have to add this user to groups with the required permissions, or assign Three roles are needed to be able to create the EKS Anywhere cluster: -1. **Create a global custom role**: For example, you could name this EKS Anywhere Global. +1. **Create a global custom role**: For example, you could name this: EKSAGlobalRole. Define it for the user on the vCenter domain level and its children objects. Create this role with the following privileges: ```