[Docs] Additional notes related EKS-A vSphere Installation
Issue #, if available: NA
Description of changes:
- The documentation for resource-pool name was incorrect which is required for EKS-A installation on vSphere
- Additional important note while using
eksctlv1.18.x on vSphere 7.0.2, as privileges are missing in v7.0.2
{
"Permissions": |-
- username: [email protected]
objectType: Folder
path: /Datacenter/vm/eksa-vms
permissions:
- ContentLibrary.AddCertToTrustStore
- ContentLibrary.DeleteCertFromTrustStore
- vSphereDataProtection.Protection
- vSphereDataProtection.Recovery
- username: [email protected]
objectType: VirtualMachine
path: /Datacenter/vm/Templates/bottlerocket-v1.25.16-kubernetes-1-25-eks-30-amd64-f19c7cc
permissions:
- ContentLibrary.AddCertToTrustStore
- ContentLibrary.DeleteCertFromTrustStore
- vSphereDataProtection.Protection
- vSphereDataProtection.Recovery
- username: [email protected]
objectType: Folder
path: /Datacenter/vm/Templates
permissions:
- ContentLibrary.AddCertToTrustStore
- ContentLibrary.DeleteCertFromTrustStore
- vSphereDataProtection.Protection
- vSphereDataProtection.Recovery
}
2024-02-14T11: 14: 09.674Z V0 ❌ Validation failed {
"validation": "vsphere Provider setup is valid",
"error": "validating vsphere user privileges: user [email protected] missing vSphere permissions",
"remediation": ""
}
Testing (if applicable): NA
Documentation added/planned (if applicable):
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: Once this PR has been reviewed and has the lgtm label, please assign csplinter for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
Hi @vrv7567. Thanks for your PR.
I'm waiting for a aws member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
@abhay-krishna I'd appreciate if this PR can be brought to notice to right set-of-eyes. This is a docs change that would save hours-of-googling while using EKS-A on vSphere
@csplinter @rothgar - from docs/OWNERS