From 68d4513c75f48357ef7feff309f5d6cffc95a529 Mon Sep 17 00:00:00 2001 From: Mike McDevitt <117493168+mimcdevitt@users.noreply.github.com> Date: Thu, 17 Oct 2024 02:46:08 -0700 Subject: [PATCH] Update docs/content/en/docs/troubleshooting/troubleshooting.md Co-authored-by: Abhay Krishna --- docs/content/en/docs/troubleshooting/troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/en/docs/troubleshooting/troubleshooting.md b/docs/content/en/docs/troubleshooting/troubleshooting.md index e19975307d83..3f72d2752cc9 100755 --- a/docs/content/en/docs/troubleshooting/troubleshooting.md +++ b/docs/content/en/docs/troubleshooting/troubleshooting.md @@ -993,7 +993,7 @@ eksa-controller-manager 1/1 1 1 4h13m #### Introduction EKS Anywhere (EKS-A) enables organizations to deploy and manage Kubernetes clusters on-premises, including in VMware vSphere environments. VMware vMotion is a feature within vSphere -e that allows live migration of virtual machines (VMs) between ESXi hypervisor hosts. This document outlines the guidelines for using vMotion to migrate EKS-A nodes between vSpher +that allows live migration of virtual machines (VMs) between ESXi hypervisor hosts. This document outlines the guidelines for using vMotion to migrate EKS-A nodes between vSphere e ESXi hosts using vMotion while ensuring cluster stability. #### Considerations for EKS-A Node Migration using vMotion