From 2d905fcf182a61e9dfea646ec3cf4bcadb6b00c0 Mon Sep 17 00:00:00 2001 From: Mike McDevitt Date: Wed, 16 Oct 2024 15:26:54 -0700 Subject: [PATCH 01/53] Add Vmotion Guidelines --- .../docs/troubleshooting/troubleshooting.md | 95 +++++++++++++++++++ 1 file changed, 95 insertions(+) diff --git a/docs/content/en/docs/troubleshooting/troubleshooting.md b/docs/content/en/docs/troubleshooting/troubleshooting.md index 8b555d983013..4bdd2ef15c68 100755 --- a/docs/content/en/docs/troubleshooting/troubleshooting.md +++ b/docs/content/en/docs/troubleshooting/troubleshooting.md @@ -988,6 +988,101 @@ $ kubectl get deployments -n eksa-system NAME READY UP-TO-DATE AVAILABLE AGE eksa-controller-manager 1/1 1 1 4h13m ``` +## VMware vSphere Best Practices for vMotion with EKS Anywhere (EKS-A) + +#### 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 vSpher +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 +e ESXi hosts using vMotion while ensuring cluster stability. + +#### Considerations for EKS-A Node Migration using vMotion + +When migrating EKS-A nodes with vMotion, several considerations must be kept in mind, particularly around configuration values defined in the [EKS-A vSphere cluster spec file](http +s://anywhere.eks.amazonaws.com/docs/getting-started/vsphere/vsphere-spec/). These configurations must remain unchanged during the migration and the infrastructure these configurati +ons represent should also not change. + + +1. **No Cross-vCenter vMotion** + +EKS-A nodes cannot be migrated between different vCenter environments using vMotion. The nodes must remain within the same vCenter instance for proper EKS-A operation. The vCenter +Server managing the EKS-A cluster is specified in the `VSphereDatacenterConfig` section of the EKS-A cluster spec file, under the `spec.server` field and cannot be changed. + + +2. **vSphere Infrastructure Settings in** `VSphereDatacenterConfig` + +In addition to the vCenter element, two additional elements defined in the `VSphereDatacenterConfig` section of the EKS-A cluster spec file are immutable must remain unchanged duri +ng the vMotion process: + + +* datacenter `(spec.datacenter)` - The datacenter specified in the EKS-A cluster spec file must not change during the vMotion migration. This value refers to the vSphere datacenter + that hosts the EKS-A nodes. + + + +* network `(spec.network)` - The network defined in the EKS-A cluster spec file must not change during the vMotion migration. This value refers the vSphere network in which the EKS +-A nodes are operating. Any changes to this network configuration would disrupt node connectivity and lead to outages in the EKS-A cluster. + + + +3. **VMware Storage vMotion is not supported for EKS-A nodes** + +datastore `(spec.datastore)` - Defined in the `VSphereMachineConfig` section of the EKS-A cluster spec file is immutable. This value refers to the vSphere datastore that holds EKS +-A node vm backing store. Modifying the datastore during vMotion (storage vMotion) would require a change to this value, which is not supported. + + +4. **Node Network Configuration Stability** + +The IP address, subnet mask, and default gateway of each EKS-A node must remain unchanged during the vMotion process. Any modifications to the IP address configuration can cause co +mmunication failures between the EKS-A nodes, pods, and the control plane, leading to disruptions in Kubernetes operations. + + +5. **EKS-A Configuration Stabiltiy** + +EKS-A environment should remain unchanged during vmotion. Do not perform or trigger any EKS-A changes or life cycle events while performing vmotion. + + +#### Best Practices for vMotion with EKS-A Clusters + +1. **Follow VMware vMotion Best Practices** + +Review VMware's general guidelines for optimal vMotion performance, such as ensuring sufficient CPU, memory, and network resources, and minimizing load on the ESXi hosts during the + migration. Refer to the [VMware vMotion documentation](https://docs.vmware.com/) for details. + +VMware vMotion Networking Best Practices: Whenever possible, follow the [Networking Best Practices for VMware vMotion](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsph +ere.vcenterhost.doc/GUID-7DAD15D4-7F41-4913-9F16-567289E22977.html) to optimize performance and reduce the risk of issues during the migration process. + +* Use High-Speed Networks: A 10GbE or higher speed network is recommended to ensure smooth vMotion operations for EKS-A nodes, particularly those with large memory footprints. + + + +2. **Shared Storage** + +Shared storage is a requirement for vmotion of EKS-A clusters. Storage such as vSAN, Fiber Channel SAN, or NFS should be shared between the supporting ESXi hosts for maintaining a +ccess to the VM's backing data without relying on storage vMotion, which is not supported in EKS-A environments. + + +3. **Monitoring Before and After Migration** + +To verify cluster health and node stability, monitor the EKS-A nodes and pods before and after the vMotion migration: + +* Before migration, run the following commands to check the current health and status of the EKS-A nodes and pods. + +``` + kubectl get nodes + kubectl get pods -a +``` + +* After vMotion activity is completed, run the command agains to verify that the nodes and pods are still operational and healthy. + + + +4. **Infrastructure Maintenance During vMotion** + +It is recommended that no other infrastructure maintenance activities be performed during the vMotion operation. The underlying datacenter infrastructure supporting the network, st +orage, and server resources utilized by Vmware vSphere must remain stable during the vMotion process. Any interruptions in these services could lead to partial or complete failures + in the vMotion process, potentially causing the EKS-A nodes to lose connectivity or experience disruptions in normal operations. + ## Snow troubleshooting From d8699bced55d0e4a01e5388e8d9dfff85a7417fd Mon Sep 17 00:00:00 2001 From: Mike McDevitt <117493168+mimcdevitt@users.noreply.github.com> Date: Thu, 17 Oct 2024 02:45:57 -0700 Subject: [PATCH 02/53] 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 4bdd2ef15c68..e19975307d83 100755 --- a/docs/content/en/docs/troubleshooting/troubleshooting.md +++ b/docs/content/en/docs/troubleshooting/troubleshooting.md @@ -992,7 +992,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 vSpher +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 e ESXi hosts using vMotion while ensuring cluster stability. 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 03/53] 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 From b7f88a3f2b299fa3b5d3709f1de4e09467b201ba Mon Sep 17 00:00:00 2001 From: Mike McDevitt <117493168+mimcdevitt@users.noreply.github.com> Date: Thu, 17 Oct 2024 02:46:17 -0700 Subject: [PATCH 04/53] 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 3f72d2752cc9..0d52719e08e3 100755 --- a/docs/content/en/docs/troubleshooting/troubleshooting.md +++ b/docs/content/en/docs/troubleshooting/troubleshooting.md @@ -998,7 +998,7 @@ e ESXi hosts using vMotion while ensuring cluster stability. #### Considerations for EKS-A Node Migration using vMotion -When migrating EKS-A nodes with vMotion, several considerations must be kept in mind, particularly around configuration values defined in the [EKS-A vSphere cluster spec file](http +When migrating EKS-A nodes with vMotion, several considerations must be kept in mind, particularly around configuration values defined in the [EKS-A vSphere cluster spec file](https://anywhere.eks.amazonaws.com/docs/getting-started/vsphere/vsphere-spec/) s://anywhere.eks.amazonaws.com/docs/getting-started/vsphere/vsphere-spec/). These configurations must remain unchanged during the migration and the infrastructure these configurati ons represent should also not change. From 6d4e4a4f4517e83a3f6ce97bdb3bd944984fa3fe Mon Sep 17 00:00:00 2001 From: Mike McDevitt <117493168+mimcdevitt@users.noreply.github.com> Date: Thu, 17 Oct 2024 02:46:29 -0700 Subject: [PATCH 05/53] 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 0d52719e08e3..f318fbf89eb0 100755 --- a/docs/content/en/docs/troubleshooting/troubleshooting.md +++ b/docs/content/en/docs/troubleshooting/troubleshooting.md @@ -999,7 +999,7 @@ e ESXi hosts using vMotion while ensuring cluster stability. #### Considerations for EKS-A Node Migration using vMotion When migrating EKS-A nodes with vMotion, several considerations must be kept in mind, particularly around configuration values defined in the [EKS-A vSphere cluster spec file](https://anywhere.eks.amazonaws.com/docs/getting-started/vsphere/vsphere-spec/) -s://anywhere.eks.amazonaws.com/docs/getting-started/vsphere/vsphere-spec/). These configurations must remain unchanged during the migration and the infrastructure these configurati +s://anywhere.eks.amazonaws.com/docs/getting-started/vsphere/vsphere-spec/). These configurations must remain unchanged during the migration and the infrastructure these configurations ons represent should also not change. From 592565aeafd8b144471e1e3742650e82f2702c89 Mon Sep 17 00:00:00 2001 From: Mike McDevitt Date: Thu, 17 Oct 2024 13:05:04 -0700 Subject: [PATCH 06/53] Adding Nodes section to Cluster management --- .../en/docs/clustermgmt/nodes/_index.md | 8 ++ .../en/docs/clustermgmt/nodes/vmotion.md | 84 +++++++++++++++++++ 2 files changed, 92 insertions(+) create mode 100644 docs/content/en/docs/clustermgmt/nodes/_index.md create mode 100755 docs/content/en/docs/clustermgmt/nodes/vmotion.md diff --git a/docs/content/en/docs/clustermgmt/nodes/_index.md b/docs/content/en/docs/clustermgmt/nodes/_index.md new file mode 100644 index 000000000000..dd4a11de61ec --- /dev/null +++ b/docs/content/en/docs/clustermgmt/nodes/_index.md @@ -0,0 +1,8 @@ +--- +title: "Nodes" +linkTitle: "Nodes" +date: 2017-01-05 +weight: 30 +description: > + Managing nodes +--- diff --git a/docs/content/en/docs/clustermgmt/nodes/vmotion.md b/docs/content/en/docs/clustermgmt/nodes/vmotion.md new file mode 100755 index 000000000000..b83912b4c168 --- /dev/null +++ b/docs/content/en/docs/clustermgmt/nodes/vmotion.md @@ -0,0 +1,84 @@ +--- +title: "VMware vSphere vMotion " +linkTitle: "VMware vSphere vMotion" +weight: 20 +description: > + Using vMotion with EKS Anywhere clusters +aliases: +--- + +## vMotion with EKS Anywhere + +#### 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 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 ESXi hosts using vMotion while ensuring cluster stability. + +#### Considerations for EKS-A Node Migration using vMotion + +When migrating EKS-A nodes with vMotion, several considerations must be kept in mind, particularly around configuration values defined in the [EKS-A vSphere cluster spec file](https://anywhere.eks.amazonaws.com/docs/getting-started/vsphere/vsphere-spec/). These configurations must remain unchanged during the migration and the infrastructure these configurations represent should also not change. + + +1. **No Cross-vCenter vMotion** + +EKS-A nodes cannot be migrated between different vCenter environments using vMotion. The nodes must remain within the same vCenter instance for proper EKS-A operation. The vCenter Server managing the EKS-A cluster is specified in the `VSphereDatacenterConfig` section of the EKS-A cluster spec file, under the `spec.server` field and cannot be changed. + + +2. **vSphere Infrastructure Settings in** `VSphereDatacenterConfig` + +In addition to the vCenter element, two additional elements defined in the `VSphereDatacenterConfig` section of the EKS-A cluster spec file are immutable must remain unchanged during the vMotion process: + + +* datacenter `(spec.datacenter)` - The datacenter specified in the EKS-A cluster spec file must not change during the vMotion migration. This value refers to the vSphere datacenter that hosts the EKS-A nodes. + + +* network `(spec.network)` - The network defined in the EKS-A cluster spec file must not change during the vMotion migration. This value refers the vSphere network in which the EKS -A nodes are operating. Any changes to this network configuration would disrupt node connectivity and lead to outages in the EKS-A cluster. + + +3. **VMware Storage vMotion is not supported for EKS-A nodes** + +datastore `(spec.datastore)` - Defined in the `VSphereMachineConfig` section of the EKS-A cluster spec file is immutable. This value refers to the vSphere datastore that holds EKS-A node vm backing store. Modifying the datastore during vMotion (storage vMotion) would require a change to this value, which is not supported. + + +4. **Node Network Configuration Stability** + +The IP address, subnet mask, and default gateway of each EKS-A node must remain unchanged during the vMotion process. Any modifications to the IP address configuration can cause communication failures between the EKS-A nodes, pods, and the control plane, leading to disruptions in EKS-A cluster operations. + + +5. **EKS-A Configuration Stabiltiy** + +EKS-A environment itself should remain unchanged during vmotion. Do not perform or trigger any EKS-A changes or life cycle events while performing vmotion. + + +#### Best Practices for vMotion with EKS-A Clusters + +1. **Follow VMware vMotion Best Practices** + +Review VMware's general guidelines for optimal vMotion performance, such as ensuring sufficient CPU, memory, and network resources, and minimizing load on the ESXi hosts during the migration. Refer to the [VMware vMotion documentation](https://docs.vmware.com/) for details. + +VMware vMotion Networking Best Practices: Whenever possible, follow the [Networking Best Practices for VMware vMotion](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vcenterhost.doc/GUID-7DAD15D4-7F41-4913-9F16-567289E22977.html) to optimize performance and reduce the risk of issues during the migration process. + +* Use High-Speed Networks: A 10GbE or higher speed network is recommended to ensure smooth vMotion operations for EKS-A nodes, particularly those with large memory footprints. + + +2. **Shared Storage** + +Shared storage is a requirement for vmotion of EKS-A clusters. Storage such as vSAN, Fiber Channel SAN, or NFS should be shared between the supporting vSphere ESXi hosts for maintaining access to the VM's backing data without relying on storage vMotion, which is not supported in EKS-A environments. + + +3. **Monitoring Before and After Migration** + +To verify cluster health and node stability, monitor the EKS-A nodes and pods before and after the vMotion migration: + +* Before migration, run the following commands to check the current health and status of the EKS-A nodes and pods. + +``` + kubectl get nodes + kubectl get pods -a +``` + +* After vMotion activity is completed, run the command agains to verify that the nodes and pods are still operational and healthy. + + +4. **Infrastructure Maintenance During vMotion** + +It is recommended that no other infrastructure maintenance activities be performed during the vMotion operation. The underlying datacenter infrastructure supporting the network, storage, and server resources utilized by VMware vSphere must remain stable during the vMotion process. Any interruptions in these services could lead to partial or complete failures in the vMotion process, potentially causing the EKS-A nodes to lose connectivity or experience disruptions in normal operations. From 056c475bf244366a72fddd0893851f29382c223a Mon Sep 17 00:00:00 2001 From: Mike McDevitt Date: Thu, 17 Oct 2024 13:06:42 -0700 Subject: [PATCH 07/53] Adding Nodes section to Cluster management --- docs/content/en/docs/clustermgmt/nodes/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/en/docs/clustermgmt/nodes/_index.md b/docs/content/en/docs/clustermgmt/nodes/_index.md index dd4a11de61ec..7e8617049d12 100644 --- a/docs/content/en/docs/clustermgmt/nodes/_index.md +++ b/docs/content/en/docs/clustermgmt/nodes/_index.md @@ -4,5 +4,5 @@ linkTitle: "Nodes" date: 2017-01-05 weight: 30 description: > - Managing nodes + Managing EKS-A nodes --- From 8b1511da22b13bc7192d9d47f1663792413dcd5e Mon Sep 17 00:00:00 2001 From: Mike McDevitt Date: Thu, 17 Oct 2024 14:59:24 -0700 Subject: [PATCH 08/53] removing vmotion section from eks-a troubleshooting --- .../docs/troubleshooting/troubleshooting.md | 95 ------------------- 1 file changed, 95 deletions(-) diff --git a/docs/content/en/docs/troubleshooting/troubleshooting.md b/docs/content/en/docs/troubleshooting/troubleshooting.md index f318fbf89eb0..8b555d983013 100755 --- a/docs/content/en/docs/troubleshooting/troubleshooting.md +++ b/docs/content/en/docs/troubleshooting/troubleshooting.md @@ -988,101 +988,6 @@ $ kubectl get deployments -n eksa-system NAME READY UP-TO-DATE AVAILABLE AGE eksa-controller-manager 1/1 1 1 4h13m ``` -## VMware vSphere Best Practices for vMotion with EKS Anywhere (EKS-A) - -#### 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 -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 - -When migrating EKS-A nodes with vMotion, several considerations must be kept in mind, particularly around configuration values defined in the [EKS-A vSphere cluster spec file](https://anywhere.eks.amazonaws.com/docs/getting-started/vsphere/vsphere-spec/) -s://anywhere.eks.amazonaws.com/docs/getting-started/vsphere/vsphere-spec/). These configurations must remain unchanged during the migration and the infrastructure these configurations -ons represent should also not change. - - -1. **No Cross-vCenter vMotion** - -EKS-A nodes cannot be migrated between different vCenter environments using vMotion. The nodes must remain within the same vCenter instance for proper EKS-A operation. The vCenter -Server managing the EKS-A cluster is specified in the `VSphereDatacenterConfig` section of the EKS-A cluster spec file, under the `spec.server` field and cannot be changed. - - -2. **vSphere Infrastructure Settings in** `VSphereDatacenterConfig` - -In addition to the vCenter element, two additional elements defined in the `VSphereDatacenterConfig` section of the EKS-A cluster spec file are immutable must remain unchanged duri -ng the vMotion process: - - -* datacenter `(spec.datacenter)` - The datacenter specified in the EKS-A cluster spec file must not change during the vMotion migration. This value refers to the vSphere datacenter - that hosts the EKS-A nodes. - - - -* network `(spec.network)` - The network defined in the EKS-A cluster spec file must not change during the vMotion migration. This value refers the vSphere network in which the EKS --A nodes are operating. Any changes to this network configuration would disrupt node connectivity and lead to outages in the EKS-A cluster. - - - -3. **VMware Storage vMotion is not supported for EKS-A nodes** - -datastore `(spec.datastore)` - Defined in the `VSphereMachineConfig` section of the EKS-A cluster spec file is immutable. This value refers to the vSphere datastore that holds EKS --A node vm backing store. Modifying the datastore during vMotion (storage vMotion) would require a change to this value, which is not supported. - - -4. **Node Network Configuration Stability** - -The IP address, subnet mask, and default gateway of each EKS-A node must remain unchanged during the vMotion process. Any modifications to the IP address configuration can cause co -mmunication failures between the EKS-A nodes, pods, and the control plane, leading to disruptions in Kubernetes operations. - - -5. **EKS-A Configuration Stabiltiy** - -EKS-A environment should remain unchanged during vmotion. Do not perform or trigger any EKS-A changes or life cycle events while performing vmotion. - - -#### Best Practices for vMotion with EKS-A Clusters - -1. **Follow VMware vMotion Best Practices** - -Review VMware's general guidelines for optimal vMotion performance, such as ensuring sufficient CPU, memory, and network resources, and minimizing load on the ESXi hosts during the - migration. Refer to the [VMware vMotion documentation](https://docs.vmware.com/) for details. - -VMware vMotion Networking Best Practices: Whenever possible, follow the [Networking Best Practices for VMware vMotion](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsph -ere.vcenterhost.doc/GUID-7DAD15D4-7F41-4913-9F16-567289E22977.html) to optimize performance and reduce the risk of issues during the migration process. - -* Use High-Speed Networks: A 10GbE or higher speed network is recommended to ensure smooth vMotion operations for EKS-A nodes, particularly those with large memory footprints. - - - -2. **Shared Storage** - -Shared storage is a requirement for vmotion of EKS-A clusters. Storage such as vSAN, Fiber Channel SAN, or NFS should be shared between the supporting ESXi hosts for maintaining a -ccess to the VM's backing data without relying on storage vMotion, which is not supported in EKS-A environments. - - -3. **Monitoring Before and After Migration** - -To verify cluster health and node stability, monitor the EKS-A nodes and pods before and after the vMotion migration: - -* Before migration, run the following commands to check the current health and status of the EKS-A nodes and pods. - -``` - kubectl get nodes - kubectl get pods -a -``` - -* After vMotion activity is completed, run the command agains to verify that the nodes and pods are still operational and healthy. - - - -4. **Infrastructure Maintenance During vMotion** - -It is recommended that no other infrastructure maintenance activities be performed during the vMotion operation. The underlying datacenter infrastructure supporting the network, st -orage, and server resources utilized by Vmware vSphere must remain stable during the vMotion process. Any interruptions in these services could lead to partial or complete failures - in the vMotion process, potentially causing the EKS-A nodes to lose connectivity or experience disruptions in normal operations. - ## Snow troubleshooting From a48152c39501eddc545df5e7e80e7490a037ab23 Mon Sep 17 00:00:00 2001 From: Mike McDevitt <117493168+mimcdevitt@users.noreply.github.com> Date: Fri, 18 Oct 2024 11:10:21 -0700 Subject: [PATCH 09/53] Update docs/content/en/docs/clustermgmt/nodes/_index.md Co-authored-by: Chris Negus --- docs/content/en/docs/clustermgmt/nodes/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/en/docs/clustermgmt/nodes/_index.md b/docs/content/en/docs/clustermgmt/nodes/_index.md index 7e8617049d12..10a38d8b1d48 100644 --- a/docs/content/en/docs/clustermgmt/nodes/_index.md +++ b/docs/content/en/docs/clustermgmt/nodes/_index.md @@ -4,5 +4,5 @@ linkTitle: "Nodes" date: 2017-01-05 weight: 30 description: > - Managing EKS-A nodes + Managing EKS Anywhere nodes --- From fcec3ee6c2898c649dcc6cc4838590e64884162c Mon Sep 17 00:00:00 2001 From: Mike McDevitt <117493168+mimcdevitt@users.noreply.github.com> Date: Fri, 18 Oct 2024 11:10:51 -0700 Subject: [PATCH 10/53] Update docs/content/en/docs/clustermgmt/nodes/vmotion.md Co-authored-by: Chris Negus --- docs/content/en/docs/clustermgmt/nodes/vmotion.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/en/docs/clustermgmt/nodes/vmotion.md b/docs/content/en/docs/clustermgmt/nodes/vmotion.md index b83912b4c168..2907ae09bfc9 100755 --- a/docs/content/en/docs/clustermgmt/nodes/vmotion.md +++ b/docs/content/en/docs/clustermgmt/nodes/vmotion.md @@ -1,5 +1,5 @@ --- -title: "VMware vSphere vMotion " +title: "Manage vSphere VMs with vMotion " linkTitle: "VMware vSphere vMotion" weight: 20 description: > From 5b50c7e935d9b3ca1d5181e99e57f2cbe7b84a31 Mon Sep 17 00:00:00 2001 From: Mike McDevitt <117493168+mimcdevitt@users.noreply.github.com> Date: Fri, 18 Oct 2024 11:11:13 -0700 Subject: [PATCH 11/53] Update docs/content/en/docs/clustermgmt/nodes/vmotion.md Co-authored-by: Chris Negus --- docs/content/en/docs/clustermgmt/nodes/vmotion.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/en/docs/clustermgmt/nodes/vmotion.md b/docs/content/en/docs/clustermgmt/nodes/vmotion.md index 2907ae09bfc9..8b135cc9705a 100755 --- a/docs/content/en/docs/clustermgmt/nodes/vmotion.md +++ b/docs/content/en/docs/clustermgmt/nodes/vmotion.md @@ -1,6 +1,6 @@ --- title: "Manage vSphere VMs with vMotion " -linkTitle: "VMware vSphere vMotion" +linkTitle: "Manage vSphere VMs" weight: 20 description: > Using vMotion with EKS Anywhere clusters From 5ba2f79c8fcce9caae7af7efbab02b7e02c91172 Mon Sep 17 00:00:00 2001 From: Mike McDevitt <117493168+mimcdevitt@users.noreply.github.com> Date: Fri, 18 Oct 2024 11:11:54 -0700 Subject: [PATCH 12/53] Update docs/content/en/docs/clustermgmt/nodes/vmotion.md Co-authored-by: Chris Negus --- docs/content/en/docs/clustermgmt/nodes/vmotion.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/en/docs/clustermgmt/nodes/vmotion.md b/docs/content/en/docs/clustermgmt/nodes/vmotion.md index 8b135cc9705a..0236a2bc8ad0 100755 --- a/docs/content/en/docs/clustermgmt/nodes/vmotion.md +++ b/docs/content/en/docs/clustermgmt/nodes/vmotion.md @@ -3,7 +3,7 @@ title: "Manage vSphere VMs with vMotion " linkTitle: "Manage vSphere VMs" weight: 20 description: > - Using vMotion with EKS Anywhere clusters + Using vMotion to manage vSphere VMs used in clusters aliases: --- From 79dd1bc2ca0bad44b0040fd6d2e4e402ff2c530f Mon Sep 17 00:00:00 2001 From: Mike McDevitt <117493168+mimcdevitt@users.noreply.github.com> Date: Fri, 18 Oct 2024 11:12:19 -0700 Subject: [PATCH 13/53] Update docs/content/en/docs/clustermgmt/nodes/vmotion.md Co-authored-by: Chris Negus --- docs/content/en/docs/clustermgmt/nodes/vmotion.md | 1 - 1 file changed, 1 deletion(-) diff --git a/docs/content/en/docs/clustermgmt/nodes/vmotion.md b/docs/content/en/docs/clustermgmt/nodes/vmotion.md index 0236a2bc8ad0..2a27a0fbc545 100755 --- a/docs/content/en/docs/clustermgmt/nodes/vmotion.md +++ b/docs/content/en/docs/clustermgmt/nodes/vmotion.md @@ -9,7 +9,6 @@ aliases: ## vMotion with EKS Anywhere -#### 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 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 ESXi hosts using vMotion while ensuring cluster stability. From 9f64b19ffead1f4c2b3666a64e84afc4b69b2ef1 Mon Sep 17 00:00:00 2001 From: Mike McDevitt <117493168+mimcdevitt@users.noreply.github.com> Date: Fri, 18 Oct 2024 11:14:04 -0700 Subject: [PATCH 14/53] Update docs/content/en/docs/clustermgmt/nodes/vmotion.md Co-authored-by: Chris Negus --- docs/content/en/docs/clustermgmt/nodes/vmotion.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/en/docs/clustermgmt/nodes/vmotion.md b/docs/content/en/docs/clustermgmt/nodes/vmotion.md index 2a27a0fbc545..43f1f40db1f1 100755 --- a/docs/content/en/docs/clustermgmt/nodes/vmotion.md +++ b/docs/content/en/docs/clustermgmt/nodes/vmotion.md @@ -71,7 +71,7 @@ To verify cluster health and node stability, monitor the EKS-A nodes and pods b * Before migration, run the following commands to check the current health and status of the EKS-A nodes and pods. ``` - kubectl get nodes + kubectl get nodes kubectl get pods -a ``` From 7747e0b04b89e039d034844d315e7bc50df059c7 Mon Sep 17 00:00:00 2001 From: Mike McDevitt <117493168+mimcdevitt@users.noreply.github.com> Date: Fri, 18 Oct 2024 11:14:12 -0700 Subject: [PATCH 15/53] Update docs/content/en/docs/clustermgmt/nodes/vmotion.md Co-authored-by: Chris Negus --- docs/content/en/docs/clustermgmt/nodes/vmotion.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/en/docs/clustermgmt/nodes/vmotion.md b/docs/content/en/docs/clustermgmt/nodes/vmotion.md index 43f1f40db1f1..cf93af5e6563 100755 --- a/docs/content/en/docs/clustermgmt/nodes/vmotion.md +++ b/docs/content/en/docs/clustermgmt/nodes/vmotion.md @@ -72,7 +72,7 @@ To verify cluster health and node stability, monitor the EKS-A nodes and pods b ``` kubectl get nodes - kubectl get pods -a + kubectl get pods -a ``` * After vMotion activity is completed, run the command agains to verify that the nodes and pods are still operational and healthy. From 5458c5c40f3a95106bd0c39b22c06126dd5bd1f0 Mon Sep 17 00:00:00 2001 From: Mike McDevitt <117493168+mimcdevitt@users.noreply.github.com> Date: Fri, 18 Oct 2024 11:14:23 -0700 Subject: [PATCH 16/53] Update docs/content/en/docs/clustermgmt/nodes/vmotion.md Co-authored-by: Chris Negus --- docs/content/en/docs/clustermgmt/nodes/vmotion.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/en/docs/clustermgmt/nodes/vmotion.md b/docs/content/en/docs/clustermgmt/nodes/vmotion.md index cf93af5e6563..68081705bad6 100755 --- a/docs/content/en/docs/clustermgmt/nodes/vmotion.md +++ b/docs/content/en/docs/clustermgmt/nodes/vmotion.md @@ -75,7 +75,7 @@ To verify cluster health and node stability, monitor the EKS-A nodes and pods b kubectl get pods -a ``` -* After vMotion activity is completed, run the command agains to verify that the nodes and pods are still operational and healthy. + * After vMotion activity is completed, run the command again to verify that the nodes and pods are still operational and healthy. 4. **Infrastructure Maintenance During vMotion** From f59543a9216ed13141ba744a4f315282d696bb9e Mon Sep 17 00:00:00 2001 From: Mike McDevitt <117493168+mimcdevitt@users.noreply.github.com> Date: Fri, 18 Oct 2024 11:14:35 -0700 Subject: [PATCH 17/53] Update docs/content/en/docs/clustermgmt/nodes/vmotion.md Co-authored-by: Chris Negus --- docs/content/en/docs/clustermgmt/nodes/vmotion.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/en/docs/clustermgmt/nodes/vmotion.md b/docs/content/en/docs/clustermgmt/nodes/vmotion.md index 68081705bad6..b766b7d72ace 100755 --- a/docs/content/en/docs/clustermgmt/nodes/vmotion.md +++ b/docs/content/en/docs/clustermgmt/nodes/vmotion.md @@ -78,6 +78,6 @@ To verify cluster health and node stability, monitor the EKS-A nodes and pods b * After vMotion activity is completed, run the command again to verify that the nodes and pods are still operational and healthy. -4. **Infrastructure Maintenance During vMotion** +* **Infrastructure maintenance during vMotion** It is recommended that no other infrastructure maintenance activities be performed during the vMotion operation. The underlying datacenter infrastructure supporting the network, storage, and server resources utilized by VMware vSphere must remain stable during the vMotion process. Any interruptions in these services could lead to partial or complete failures in the vMotion process, potentially causing the EKS-A nodes to lose connectivity or experience disruptions in normal operations. From 83ac1785ccfc36f46c665cb8fa2ea610024f8196 Mon Sep 17 00:00:00 2001 From: Mike McDevitt <117493168+mimcdevitt@users.noreply.github.com> Date: Sat, 19 Oct 2024 00:10:00 -0700 Subject: [PATCH 18/53] Update docs/content/en/docs/clustermgmt/nodes/vmotion.md Co-authored-by: Chris Negus --- docs/content/en/docs/clustermgmt/nodes/vmotion.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/en/docs/clustermgmt/nodes/vmotion.md b/docs/content/en/docs/clustermgmt/nodes/vmotion.md index b766b7d72ace..b77532b04d6e 100755 --- a/docs/content/en/docs/clustermgmt/nodes/vmotion.md +++ b/docs/content/en/docs/clustermgmt/nodes/vmotion.md @@ -80,4 +80,4 @@ To verify cluster health and node stability, monitor the EKS-A nodes and pods b * **Infrastructure maintenance during vMotion** -It is recommended that no other infrastructure maintenance activities be performed during the vMotion operation. The underlying datacenter infrastructure supporting the network, storage, and server resources utilized by VMware vSphere must remain stable during the vMotion process. Any interruptions in these services could lead to partial or complete failures in the vMotion process, potentially causing the EKS-A nodes to lose connectivity or experience disruptions in normal operations. + It is recommended that no other infrastructure maintenance activities be performed during the vMotion operation. The underlying datacenter infrastructure supporting the network, storage, and server resources utilized by VMware vSphere must remain stable during the vMotion process. Any interruptions in these services could lead to partial or complete failures in the vMotion process, potentially causing the EKS Anywhere nodes to lose connectivity or experience disruptions in normal operations. From c1ea995dba52c93b2b9a1ab48370a8487e3bd1a9 Mon Sep 17 00:00:00 2001 From: Mike McDevitt <117493168+mimcdevitt@users.noreply.github.com> Date: Mon, 21 Oct 2024 10:26:35 -0700 Subject: [PATCH 19/53] Update docs/content/en/docs/clustermgmt/nodes/vmotion.md Co-authored-by: Chris Negus --- docs/content/en/docs/clustermgmt/nodes/vmotion.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/en/docs/clustermgmt/nodes/vmotion.md b/docs/content/en/docs/clustermgmt/nodes/vmotion.md index b77532b04d6e..ea3e0e1e8fba 100755 --- a/docs/content/en/docs/clustermgmt/nodes/vmotion.md +++ b/docs/content/en/docs/clustermgmt/nodes/vmotion.md @@ -10,7 +10,7 @@ aliases: ## vMotion with EKS Anywhere -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 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 ESXi hosts using vMotion while ensuring cluster stability. +VMware vMotion is a feature within vSphere that allows live migration of virtual machines (VMs) between ESXi hypervisor hosts. This document outlines the guidelines for using vMotion to migrate EKS Anywhere nodes between vSphere ESXi hosts using vMotion while ensuring cluster stability. #### Considerations for EKS-A Node Migration using vMotion From a05c24c9b8fb155b517e88c21a34cef4644eaadd Mon Sep 17 00:00:00 2001 From: Mike McDevitt <117493168+mimcdevitt@users.noreply.github.com> Date: Mon, 21 Oct 2024 10:30:05 -0700 Subject: [PATCH 20/53] Update docs/content/en/docs/clustermgmt/nodes/vmotion.md Co-authored-by: Chris Negus --- docs/content/en/docs/clustermgmt/nodes/vmotion.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/en/docs/clustermgmt/nodes/vmotion.md b/docs/content/en/docs/clustermgmt/nodes/vmotion.md index ea3e0e1e8fba..f7641aaf7c63 100755 --- a/docs/content/en/docs/clustermgmt/nodes/vmotion.md +++ b/docs/content/en/docs/clustermgmt/nodes/vmotion.md @@ -12,7 +12,7 @@ aliases: VMware vMotion is a feature within vSphere that allows live migration of virtual machines (VMs) between ESXi hypervisor hosts. This document outlines the guidelines for using vMotion to migrate EKS Anywhere nodes between vSphere ESXi hosts using vMotion while ensuring cluster stability. -#### Considerations for EKS-A Node Migration using vMotion +### Considerations for node migration using vMotion When migrating EKS-A nodes with vMotion, several considerations must be kept in mind, particularly around configuration values defined in the [EKS-A vSphere cluster spec file](https://anywhere.eks.amazonaws.com/docs/getting-started/vsphere/vsphere-spec/). These configurations must remain unchanged during the migration and the infrastructure these configurations represent should also not change. From d5cf4f07f73617bb1af4cf1bb5c69455a80b4fd4 Mon Sep 17 00:00:00 2001 From: Mike McDevitt <117493168+mimcdevitt@users.noreply.github.com> Date: Mon, 21 Oct 2024 10:31:42 -0700 Subject: [PATCH 21/53] Update docs/content/en/docs/clustermgmt/nodes/vmotion.md Co-authored-by: Chris Negus --- docs/content/en/docs/clustermgmt/nodes/vmotion.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/en/docs/clustermgmt/nodes/vmotion.md b/docs/content/en/docs/clustermgmt/nodes/vmotion.md index f7641aaf7c63..0c7e6314fe28 100755 --- a/docs/content/en/docs/clustermgmt/nodes/vmotion.md +++ b/docs/content/en/docs/clustermgmt/nodes/vmotion.md @@ -14,7 +14,7 @@ VMware vMotion is a feature within vSphere that allows live migration of virtual ### Considerations for node migration using vMotion -When migrating EKS-A nodes with vMotion, several considerations must be kept in mind, particularly around configuration values defined in the [EKS-A vSphere cluster spec file](https://anywhere.eks.amazonaws.com/docs/getting-started/vsphere/vsphere-spec/). These configurations must remain unchanged during the migration and the infrastructure these configurations represent should also not change. +When migrating EKS Anywhere nodes with vMotion, several considerations must be kept in mind, particularly around configuration values defined in the [vSphere cluster spec file]({{< relref "/docs/getting-started/vsphere/vsphere-spec" >}}) . These configurations must remain unchanged during the migration and the infrastructure these configurations represent should also not change. 1. **No Cross-vCenter vMotion** From b2c4e54e6f4a019e3017e5a70764b9e863a72cce Mon Sep 17 00:00:00 2001 From: Mike McDevitt <117493168+mimcdevitt@users.noreply.github.com> Date: Mon, 21 Oct 2024 10:36:42 -0700 Subject: [PATCH 22/53] Update docs/content/en/docs/clustermgmt/nodes/vmotion.md Co-authored-by: Chris Negus --- docs/content/en/docs/clustermgmt/nodes/vmotion.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/en/docs/clustermgmt/nodes/vmotion.md b/docs/content/en/docs/clustermgmt/nodes/vmotion.md index 0c7e6314fe28..91c4e7a4bbba 100755 --- a/docs/content/en/docs/clustermgmt/nodes/vmotion.md +++ b/docs/content/en/docs/clustermgmt/nodes/vmotion.md @@ -17,7 +17,7 @@ VMware vMotion is a feature within vSphere that allows live migration of virtual When migrating EKS Anywhere nodes with vMotion, several considerations must be kept in mind, particularly around configuration values defined in the [vSphere cluster spec file]({{< relref "/docs/getting-started/vsphere/vsphere-spec" >}}) . These configurations must remain unchanged during the migration and the infrastructure these configurations represent should also not change. -1. **No Cross-vCenter vMotion** +* **No cross-vCenter vMotion** EKS-A nodes cannot be migrated between different vCenter environments using vMotion. The nodes must remain within the same vCenter instance for proper EKS-A operation. The vCenter Server managing the EKS-A cluster is specified in the `VSphereDatacenterConfig` section of the EKS-A cluster spec file, under the `spec.server` field and cannot be changed. From 275f7e9b94140e25451f3302422cf2d208b7b4b0 Mon Sep 17 00:00:00 2001 From: Mike McDevitt <117493168+mimcdevitt@users.noreply.github.com> Date: Mon, 21 Oct 2024 10:38:42 -0700 Subject: [PATCH 23/53] Update docs/content/en/docs/clustermgmt/nodes/vmotion.md Co-authored-by: Chris Negus --- docs/content/en/docs/clustermgmt/nodes/vmotion.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/en/docs/clustermgmt/nodes/vmotion.md b/docs/content/en/docs/clustermgmt/nodes/vmotion.md index 91c4e7a4bbba..f5d6862520ac 100755 --- a/docs/content/en/docs/clustermgmt/nodes/vmotion.md +++ b/docs/content/en/docs/clustermgmt/nodes/vmotion.md @@ -19,7 +19,7 @@ When migrating EKS Anywhere nodes with vMotion, several considerations must be k * **No cross-vCenter vMotion** -EKS-A nodes cannot be migrated between different vCenter environments using vMotion. The nodes must remain within the same vCenter instance for proper EKS-A operation. The vCenter Server managing the EKS-A cluster is specified in the `VSphereDatacenterConfig` section of the EKS-A cluster spec file, under the `spec.server` field and cannot be changed. +EKS Anywhere nodes cannot be migrated between different vCenter environments using vMotion. The nodes must remain within the same vCenter instance for proper EKS Anywhere operation. The vCenter Server managing the EKS Anywhere cluster is specified in the `VSphereDatacenterConfig` section of the EKS Anywhere [vSphere cluster spec file]({{< relref "/docs/getting-started/vsphere/vsphere-spec" >}}), under the `spec.server` field, and cannot be changed. 2. **vSphere Infrastructure Settings in** `VSphereDatacenterConfig` From 3b9444471244283a76ac7d78f6ffd32e32626dcd Mon Sep 17 00:00:00 2001 From: Mike McDevitt <117493168+mimcdevitt@users.noreply.github.com> Date: Mon, 21 Oct 2024 10:39:02 -0700 Subject: [PATCH 24/53] Update docs/content/en/docs/clustermgmt/nodes/vmotion.md Co-authored-by: Chris Negus --- docs/content/en/docs/clustermgmt/nodes/vmotion.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/en/docs/clustermgmt/nodes/vmotion.md b/docs/content/en/docs/clustermgmt/nodes/vmotion.md index f5d6862520ac..93c400017709 100755 --- a/docs/content/en/docs/clustermgmt/nodes/vmotion.md +++ b/docs/content/en/docs/clustermgmt/nodes/vmotion.md @@ -22,7 +22,7 @@ When migrating EKS Anywhere nodes with vMotion, several considerations must be k EKS Anywhere nodes cannot be migrated between different vCenter environments using vMotion. The nodes must remain within the same vCenter instance for proper EKS Anywhere operation. The vCenter Server managing the EKS Anywhere cluster is specified in the `VSphereDatacenterConfig` section of the EKS Anywhere [vSphere cluster spec file]({{< relref "/docs/getting-started/vsphere/vsphere-spec" >}}), under the `spec.server` field, and cannot be changed. -2. **vSphere Infrastructure Settings in** `VSphereDatacenterConfig` +* **vSphere infrastructure settings in** `VSphereDatacenterConfig` In addition to the vCenter element, two additional elements defined in the `VSphereDatacenterConfig` section of the EKS-A cluster spec file are immutable must remain unchanged during the vMotion process: From 9baf914cb67592128e271b63d5f35545dcff352d Mon Sep 17 00:00:00 2001 From: Mike McDevitt <117493168+mimcdevitt@users.noreply.github.com> Date: Mon, 21 Oct 2024 10:57:06 -0700 Subject: [PATCH 25/53] Update docs/content/en/docs/clustermgmt/nodes/vmotion.md Co-authored-by: Chris Negus --- docs/content/en/docs/clustermgmt/nodes/vmotion.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/en/docs/clustermgmt/nodes/vmotion.md b/docs/content/en/docs/clustermgmt/nodes/vmotion.md index 93c400017709..45750cd08fc8 100755 --- a/docs/content/en/docs/clustermgmt/nodes/vmotion.md +++ b/docs/content/en/docs/clustermgmt/nodes/vmotion.md @@ -27,7 +27,7 @@ EKS Anywhere nodes cannot be migrated between different vCenter environments usi In addition to the vCenter element, two additional elements defined in the `VSphereDatacenterConfig` section of the EKS-A cluster spec file are immutable must remain unchanged during the vMotion process: -* datacenter `(spec.datacenter)` - The datacenter specified in the EKS-A cluster spec file must not change during the vMotion migration. This value refers to the vSphere datacenter that hosts the EKS-A nodes. + * datacenter `(spec.datacenter)` - The datacenter specified in the EKS Anywhere cluster spec file must not change during the vMotion migration. This value refers to the vSphere datacenter that hosts the EKS Anywhere nodes. * network `(spec.network)` - The network defined in the EKS-A cluster spec file must not change during the vMotion migration. This value refers the vSphere network in which the EKS -A nodes are operating. Any changes to this network configuration would disrupt node connectivity and lead to outages in the EKS-A cluster. From aeb187f6a4645134b5abc7ee3d622c8de161a4f2 Mon Sep 17 00:00:00 2001 From: Mike McDevitt <117493168+mimcdevitt@users.noreply.github.com> Date: Mon, 21 Oct 2024 10:57:17 -0700 Subject: [PATCH 26/53] Update docs/content/en/docs/clustermgmt/nodes/vmotion.md Co-authored-by: Chris Negus --- docs/content/en/docs/clustermgmt/nodes/vmotion.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/en/docs/clustermgmt/nodes/vmotion.md b/docs/content/en/docs/clustermgmt/nodes/vmotion.md index 45750cd08fc8..4a0aa5560551 100755 --- a/docs/content/en/docs/clustermgmt/nodes/vmotion.md +++ b/docs/content/en/docs/clustermgmt/nodes/vmotion.md @@ -24,7 +24,7 @@ EKS Anywhere nodes cannot be migrated between different vCenter environments usi * **vSphere infrastructure settings in** `VSphereDatacenterConfig` -In addition to the vCenter element, two additional elements defined in the `VSphereDatacenterConfig` section of the EKS-A cluster spec file are immutable must remain unchanged during the vMotion process: + In addition to the vCenter element, two additional elements defined in the `VSphereDatacenterConfig` section of the EKS Anywhere cluster spec file are immutable must remain unchanged during the vMotion process: * datacenter `(spec.datacenter)` - The datacenter specified in the EKS Anywhere cluster spec file must not change during the vMotion migration. This value refers to the vSphere datacenter that hosts the EKS Anywhere nodes. From fc6215f3fe90f4728f3e8dd908ff40f6b3ffe28f Mon Sep 17 00:00:00 2001 From: Mike McDevitt <117493168+mimcdevitt@users.noreply.github.com> Date: Mon, 21 Oct 2024 10:57:27 -0700 Subject: [PATCH 27/53] Update docs/content/en/docs/clustermgmt/nodes/vmotion.md Co-authored-by: Chris Negus --- docs/content/en/docs/clustermgmt/nodes/vmotion.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/en/docs/clustermgmt/nodes/vmotion.md b/docs/content/en/docs/clustermgmt/nodes/vmotion.md index 4a0aa5560551..1ac5e9ccf2cf 100755 --- a/docs/content/en/docs/clustermgmt/nodes/vmotion.md +++ b/docs/content/en/docs/clustermgmt/nodes/vmotion.md @@ -30,7 +30,7 @@ EKS Anywhere nodes cannot be migrated between different vCenter environments usi * datacenter `(spec.datacenter)` - The datacenter specified in the EKS Anywhere cluster spec file must not change during the vMotion migration. This value refers to the vSphere datacenter that hosts the EKS Anywhere nodes. -* network `(spec.network)` - The network defined in the EKS-A cluster spec file must not change during the vMotion migration. This value refers the vSphere network in which the EKS -A nodes are operating. Any changes to this network configuration would disrupt node connectivity and lead to outages in the EKS-A cluster. + * network `(spec.network)` - The network defined in the EKS Anywhere cluster spec file must not change during the vMotion migration. This value refers the vSphere network in which the EKS Anywhere nodes are operating. Any changes to this network configuration would disrupt node connectivity and lead to outages in the EKS Anywhere cluster. 3. **VMware Storage vMotion is not supported for EKS-A nodes** From 1b7ee634da4d3841c9379b6d364bbad4db063cc5 Mon Sep 17 00:00:00 2001 From: Mike McDevitt <117493168+mimcdevitt@users.noreply.github.com> Date: Mon, 21 Oct 2024 10:57:35 -0700 Subject: [PATCH 28/53] Update docs/content/en/docs/clustermgmt/nodes/vmotion.md Co-authored-by: Chris Negus --- docs/content/en/docs/clustermgmt/nodes/vmotion.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/en/docs/clustermgmt/nodes/vmotion.md b/docs/content/en/docs/clustermgmt/nodes/vmotion.md index 1ac5e9ccf2cf..788a778112df 100755 --- a/docs/content/en/docs/clustermgmt/nodes/vmotion.md +++ b/docs/content/en/docs/clustermgmt/nodes/vmotion.md @@ -33,7 +33,7 @@ EKS Anywhere nodes cannot be migrated between different vCenter environments usi * network `(spec.network)` - The network defined in the EKS Anywhere cluster spec file must not change during the vMotion migration. This value refers the vSphere network in which the EKS Anywhere nodes are operating. Any changes to this network configuration would disrupt node connectivity and lead to outages in the EKS Anywhere cluster. -3. **VMware Storage vMotion is not supported for EKS-A nodes** +* **VMware Storage vMotion is not supported for EKS Anywhere nodes** datastore `(spec.datastore)` - Defined in the `VSphereMachineConfig` section of the EKS-A cluster spec file is immutable. This value refers to the vSphere datastore that holds EKS-A node vm backing store. Modifying the datastore during vMotion (storage vMotion) would require a change to this value, which is not supported. From c96511dd1631b4d12fa9699c8862e23de2aebb3e Mon Sep 17 00:00:00 2001 From: Mike McDevitt <117493168+mimcdevitt@users.noreply.github.com> Date: Mon, 21 Oct 2024 10:57:44 -0700 Subject: [PATCH 29/53] Update docs/content/en/docs/clustermgmt/nodes/vmotion.md Co-authored-by: Chris Negus --- docs/content/en/docs/clustermgmt/nodes/vmotion.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/en/docs/clustermgmt/nodes/vmotion.md b/docs/content/en/docs/clustermgmt/nodes/vmotion.md index 788a778112df..6c7dcbbe00bc 100755 --- a/docs/content/en/docs/clustermgmt/nodes/vmotion.md +++ b/docs/content/en/docs/clustermgmt/nodes/vmotion.md @@ -35,7 +35,7 @@ EKS Anywhere nodes cannot be migrated between different vCenter environments usi * **VMware Storage vMotion is not supported for EKS Anywhere nodes** -datastore `(spec.datastore)` - Defined in the `VSphereMachineConfig` section of the EKS-A cluster spec file is immutable. This value refers to the vSphere datastore that holds EKS-A node vm backing store. Modifying the datastore during vMotion (storage vMotion) would require a change to this value, which is not supported. + datastore `(spec.datastore)` - Defined in the `VSphereMachineConfig` section of the EKS Anywhere cluster spec file is immutable. This value refers to the vSphere datastore that holds EKS Anywhere node vm backing store. Modifying the datastore during vMotion (storage vMotion) would require a change to this value, which is not supported. 4. **Node Network Configuration Stability** From 526dc37dd57fb776468d01bba949448ef7fd0ff3 Mon Sep 17 00:00:00 2001 From: Mike McDevitt <117493168+mimcdevitt@users.noreply.github.com> Date: Mon, 21 Oct 2024 10:57:51 -0700 Subject: [PATCH 30/53] Update docs/content/en/docs/clustermgmt/nodes/vmotion.md Co-authored-by: Chris Negus --- docs/content/en/docs/clustermgmt/nodes/vmotion.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/en/docs/clustermgmt/nodes/vmotion.md b/docs/content/en/docs/clustermgmt/nodes/vmotion.md index 6c7dcbbe00bc..e65f90f0e71d 100755 --- a/docs/content/en/docs/clustermgmt/nodes/vmotion.md +++ b/docs/content/en/docs/clustermgmt/nodes/vmotion.md @@ -38,7 +38,7 @@ EKS Anywhere nodes cannot be migrated between different vCenter environments usi datastore `(spec.datastore)` - Defined in the `VSphereMachineConfig` section of the EKS Anywhere cluster spec file is immutable. This value refers to the vSphere datastore that holds EKS Anywhere node vm backing store. Modifying the datastore during vMotion (storage vMotion) would require a change to this value, which is not supported. -4. **Node Network Configuration Stability** +* **Node network configuration stability** The IP address, subnet mask, and default gateway of each EKS-A node must remain unchanged during the vMotion process. Any modifications to the IP address configuration can cause communication failures between the EKS-A nodes, pods, and the control plane, leading to disruptions in EKS-A cluster operations. From eae6edd14e63d26bbc48376dba6e1ddd1ea47347 Mon Sep 17 00:00:00 2001 From: Mike McDevitt <117493168+mimcdevitt@users.noreply.github.com> Date: Mon, 21 Oct 2024 10:57:57 -0700 Subject: [PATCH 31/53] Update docs/content/en/docs/clustermgmt/nodes/vmotion.md Co-authored-by: Chris Negus --- docs/content/en/docs/clustermgmt/nodes/vmotion.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/en/docs/clustermgmt/nodes/vmotion.md b/docs/content/en/docs/clustermgmt/nodes/vmotion.md index e65f90f0e71d..7f7ebe632af9 100755 --- a/docs/content/en/docs/clustermgmt/nodes/vmotion.md +++ b/docs/content/en/docs/clustermgmt/nodes/vmotion.md @@ -40,7 +40,7 @@ EKS Anywhere nodes cannot be migrated between different vCenter environments usi * **Node network configuration stability** -The IP address, subnet mask, and default gateway of each EKS-A node must remain unchanged during the vMotion process. Any modifications to the IP address configuration can cause communication failures between the EKS-A nodes, pods, and the control plane, leading to disruptions in EKS-A cluster operations. + The IP address, subnet mask, and default gateway of each EKS Anywhere node must remain unchanged during the vMotion process. Any modifications to the IP address configuration can cause communication failures between the EKS Anywhere nodes, pods, and the control plane, leading to disruptions in EKS Anywhere cluster operations. 5. **EKS-A Configuration Stabiltiy** From e3535838432acd820b46e94d369c8f7d61cbb23f Mon Sep 17 00:00:00 2001 From: Mike McDevitt <117493168+mimcdevitt@users.noreply.github.com> Date: Mon, 21 Oct 2024 10:58:23 -0700 Subject: [PATCH 32/53] Update docs/content/en/docs/clustermgmt/nodes/vmotion.md Co-authored-by: Chris Negus --- docs/content/en/docs/clustermgmt/nodes/vmotion.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/en/docs/clustermgmt/nodes/vmotion.md b/docs/content/en/docs/clustermgmt/nodes/vmotion.md index 7f7ebe632af9..3ff1a0134322 100755 --- a/docs/content/en/docs/clustermgmt/nodes/vmotion.md +++ b/docs/content/en/docs/clustermgmt/nodes/vmotion.md @@ -43,7 +43,7 @@ EKS Anywhere nodes cannot be migrated between different vCenter environments usi The IP address, subnet mask, and default gateway of each EKS Anywhere node must remain unchanged during the vMotion process. Any modifications to the IP address configuration can cause communication failures between the EKS Anywhere nodes, pods, and the control plane, leading to disruptions in EKS Anywhere cluster operations. -5. **EKS-A Configuration Stabiltiy** +* **EKS Anywhere configuration stabiltiy** EKS-A environment itself should remain unchanged during vmotion. Do not perform or trigger any EKS-A changes or life cycle events while performing vmotion. From 33fabf8c7e08b69832caf83393411def575d3162 Mon Sep 17 00:00:00 2001 From: Mike McDevitt <117493168+mimcdevitt@users.noreply.github.com> Date: Mon, 21 Oct 2024 11:13:18 -0700 Subject: [PATCH 33/53] Update docs/content/en/docs/clustermgmt/nodes/vmotion.md Co-authored-by: Chris Negus --- docs/content/en/docs/clustermgmt/nodes/vmotion.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/en/docs/clustermgmt/nodes/vmotion.md b/docs/content/en/docs/clustermgmt/nodes/vmotion.md index 3ff1a0134322..5c6633e3814c 100755 --- a/docs/content/en/docs/clustermgmt/nodes/vmotion.md +++ b/docs/content/en/docs/clustermgmt/nodes/vmotion.md @@ -45,7 +45,7 @@ EKS Anywhere nodes cannot be migrated between different vCenter environments usi * **EKS Anywhere configuration stabiltiy** -EKS-A environment itself should remain unchanged during vmotion. Do not perform or trigger any EKS-A changes or life cycle events while performing vmotion. + The EKS Anywhere environment itself should remain unchanged during vmotion. Do not perform or trigger any EKS Anywhere changes or life cycle events while performing vmotion. #### Best Practices for vMotion with EKS-A Clusters From 5d850fc34f0eb6fca1f53edd092de8303d5ae9d1 Mon Sep 17 00:00:00 2001 From: Mike McDevitt <117493168+mimcdevitt@users.noreply.github.com> Date: Mon, 21 Oct 2024 11:13:30 -0700 Subject: [PATCH 34/53] Update docs/content/en/docs/clustermgmt/nodes/vmotion.md Co-authored-by: Chris Negus --- docs/content/en/docs/clustermgmt/nodes/vmotion.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/en/docs/clustermgmt/nodes/vmotion.md b/docs/content/en/docs/clustermgmt/nodes/vmotion.md index 5c6633e3814c..d8e2b1920963 100755 --- a/docs/content/en/docs/clustermgmt/nodes/vmotion.md +++ b/docs/content/en/docs/clustermgmt/nodes/vmotion.md @@ -48,7 +48,7 @@ EKS Anywhere nodes cannot be migrated between different vCenter environments usi The EKS Anywhere environment itself should remain unchanged during vmotion. Do not perform or trigger any EKS Anywhere changes or life cycle events while performing vmotion. -#### Best Practices for vMotion with EKS-A Clusters +### Best practices for vMotion with EKS Anywhere clusters 1. **Follow VMware vMotion Best Practices** From 650de44355fa97cd82d27d0ff3835069f766b3a7 Mon Sep 17 00:00:00 2001 From: Mike McDevitt <117493168+mimcdevitt@users.noreply.github.com> Date: Mon, 21 Oct 2024 11:13:39 -0700 Subject: [PATCH 35/53] Update docs/content/en/docs/clustermgmt/nodes/vmotion.md Co-authored-by: Chris Negus --- docs/content/en/docs/clustermgmt/nodes/vmotion.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/en/docs/clustermgmt/nodes/vmotion.md b/docs/content/en/docs/clustermgmt/nodes/vmotion.md index d8e2b1920963..fcc414130b43 100755 --- a/docs/content/en/docs/clustermgmt/nodes/vmotion.md +++ b/docs/content/en/docs/clustermgmt/nodes/vmotion.md @@ -50,7 +50,7 @@ EKS Anywhere nodes cannot be migrated between different vCenter environments usi ### Best practices for vMotion with EKS Anywhere clusters -1. **Follow VMware vMotion Best Practices** +* **Follow VMware vMotion best practices** Review VMware's general guidelines for optimal vMotion performance, such as ensuring sufficient CPU, memory, and network resources, and minimizing load on the ESXi hosts during the migration. Refer to the [VMware vMotion documentation](https://docs.vmware.com/) for details. From cee5afae2962e18901a9ae078bf756e4ca561042 Mon Sep 17 00:00:00 2001 From: Mike McDevitt <117493168+mimcdevitt@users.noreply.github.com> Date: Mon, 21 Oct 2024 11:24:10 -0700 Subject: [PATCH 36/53] Update docs/content/en/docs/clustermgmt/nodes/vmotion.md Co-authored-by: Chris Negus --- docs/content/en/docs/clustermgmt/nodes/vmotion.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/en/docs/clustermgmt/nodes/vmotion.md b/docs/content/en/docs/clustermgmt/nodes/vmotion.md index fcc414130b43..ee3c1e897732 100755 --- a/docs/content/en/docs/clustermgmt/nodes/vmotion.md +++ b/docs/content/en/docs/clustermgmt/nodes/vmotion.md @@ -54,7 +54,7 @@ EKS Anywhere nodes cannot be migrated between different vCenter environments usi Review VMware's general guidelines for optimal vMotion performance, such as ensuring sufficient CPU, memory, and network resources, and minimizing load on the ESXi hosts during the migration. Refer to the [VMware vMotion documentation](https://docs.vmware.com/) for details. -VMware vMotion Networking Best Practices: Whenever possible, follow the [Networking Best Practices for VMware vMotion](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vcenterhost.doc/GUID-7DAD15D4-7F41-4913-9F16-567289E22977.html) to optimize performance and reduce the risk of issues during the migration process. + * VMware vMotion Networking Best Practices: Whenever possible, follow the [Networking Best Practices for VMware vMotion](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vcenterhost.doc/GUID-7DAD15D4-7F41-4913-9F16-567289E22977.html) to optimize performance and reduce the risk of issues during the migration process. * Use High-Speed Networks: A 10GbE or higher speed network is recommended to ensure smooth vMotion operations for EKS-A nodes, particularly those with large memory footprints. From b0e62d09597ae38dde586b725463535eb70f870d Mon Sep 17 00:00:00 2001 From: Mike McDevitt <117493168+mimcdevitt@users.noreply.github.com> Date: Mon, 21 Oct 2024 11:24:17 -0700 Subject: [PATCH 37/53] Update docs/content/en/docs/clustermgmt/nodes/vmotion.md Co-authored-by: Chris Negus --- docs/content/en/docs/clustermgmt/nodes/vmotion.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/en/docs/clustermgmt/nodes/vmotion.md b/docs/content/en/docs/clustermgmt/nodes/vmotion.md index ee3c1e897732..5ba765816c69 100755 --- a/docs/content/en/docs/clustermgmt/nodes/vmotion.md +++ b/docs/content/en/docs/clustermgmt/nodes/vmotion.md @@ -52,7 +52,7 @@ EKS Anywhere nodes cannot be migrated between different vCenter environments usi * **Follow VMware vMotion best practices** -Review VMware's general guidelines for optimal vMotion performance, such as ensuring sufficient CPU, memory, and network resources, and minimizing load on the ESXi hosts during the migration. Refer to the [VMware vMotion documentation](https://docs.vmware.com/) for details. + * General best practices: Review VMware's general guidelines for optimal vMotion performance, such as ensuring sufficient CPU, memory, and network resources, and minimizing load on the ESXi hosts during the migration. Refer to the [VMware vMotion documentation](https://docs.vmware.com/) for details. * VMware vMotion Networking Best Practices: Whenever possible, follow the [Networking Best Practices for VMware vMotion](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vcenterhost.doc/GUID-7DAD15D4-7F41-4913-9F16-567289E22977.html) to optimize performance and reduce the risk of issues during the migration process. From f56e24edfcbcdfa9946721e3106a2502c110e2e1 Mon Sep 17 00:00:00 2001 From: Mike McDevitt <117493168+mimcdevitt@users.noreply.github.com> Date: Mon, 21 Oct 2024 11:24:26 -0700 Subject: [PATCH 38/53] Update docs/content/en/docs/clustermgmt/nodes/vmotion.md Co-authored-by: Chris Negus --- docs/content/en/docs/clustermgmt/nodes/vmotion.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/en/docs/clustermgmt/nodes/vmotion.md b/docs/content/en/docs/clustermgmt/nodes/vmotion.md index 5ba765816c69..849260209528 100755 --- a/docs/content/en/docs/clustermgmt/nodes/vmotion.md +++ b/docs/content/en/docs/clustermgmt/nodes/vmotion.md @@ -56,7 +56,7 @@ EKS Anywhere nodes cannot be migrated between different vCenter environments usi * VMware vMotion Networking Best Practices: Whenever possible, follow the [Networking Best Practices for VMware vMotion](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vcenterhost.doc/GUID-7DAD15D4-7F41-4913-9F16-567289E22977.html) to optimize performance and reduce the risk of issues during the migration process. -* Use High-Speed Networks: A 10GbE or higher speed network is recommended to ensure smooth vMotion operations for EKS-A nodes, particularly those with large memory footprints. + * Use High-Speed Networks: A 10GbE or higher speed network is recommended to ensure smooth vMotion operations for EKS-A nodes, particularly those with large memory footprints. 2. **Shared Storage** From 6d45346fd09a08141519de30412c429e25ad484e Mon Sep 17 00:00:00 2001 From: Mike McDevitt <117493168+mimcdevitt@users.noreply.github.com> Date: Mon, 21 Oct 2024 11:24:35 -0700 Subject: [PATCH 39/53] Update docs/content/en/docs/clustermgmt/nodes/vmotion.md Co-authored-by: Chris Negus --- docs/content/en/docs/clustermgmt/nodes/vmotion.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/en/docs/clustermgmt/nodes/vmotion.md b/docs/content/en/docs/clustermgmt/nodes/vmotion.md index 849260209528..74e959a11ef8 100755 --- a/docs/content/en/docs/clustermgmt/nodes/vmotion.md +++ b/docs/content/en/docs/clustermgmt/nodes/vmotion.md @@ -59,7 +59,7 @@ EKS Anywhere nodes cannot be migrated between different vCenter environments usi * Use High-Speed Networks: A 10GbE or higher speed network is recommended to ensure smooth vMotion operations for EKS-A nodes, particularly those with large memory footprints. -2. **Shared Storage** +* **Shared Storage** Shared storage is a requirement for vmotion of EKS-A clusters. Storage such as vSAN, Fiber Channel SAN, or NFS should be shared between the supporting vSphere ESXi hosts for maintaining access to the VM's backing data without relying on storage vMotion, which is not supported in EKS-A environments. From ba046266c0be0a4cd2a514c625dd64bd1f65cbc4 Mon Sep 17 00:00:00 2001 From: Mike McDevitt <117493168+mimcdevitt@users.noreply.github.com> Date: Mon, 21 Oct 2024 11:24:45 -0700 Subject: [PATCH 40/53] Update docs/content/en/docs/clustermgmt/nodes/vmotion.md Co-authored-by: Chris Negus --- docs/content/en/docs/clustermgmt/nodes/vmotion.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/en/docs/clustermgmt/nodes/vmotion.md b/docs/content/en/docs/clustermgmt/nodes/vmotion.md index 74e959a11ef8..7d4274258309 100755 --- a/docs/content/en/docs/clustermgmt/nodes/vmotion.md +++ b/docs/content/en/docs/clustermgmt/nodes/vmotion.md @@ -61,7 +61,7 @@ EKS Anywhere nodes cannot be migrated between different vCenter environments usi * **Shared Storage** -Shared storage is a requirement for vmotion of EKS-A clusters. Storage such as vSAN, Fiber Channel SAN, or NFS should be shared between the supporting vSphere ESXi hosts for maintaining access to the VM's backing data without relying on storage vMotion, which is not supported in EKS-A environments. + Shared storage is a requirement for vmotion of EKS-A clusters. Storage such as vSAN, Fiber Channel SAN, or NFS should be shared between the supporting vSphere ESXi hosts for maintaining access to the VM's backing data without relying on storage vMotion, which is not supported in EKS-A environments. 3. **Monitoring Before and After Migration** From f24b470fb922a87e7b0e9832b1b90cd3110f6cd2 Mon Sep 17 00:00:00 2001 From: Mike McDevitt <117493168+mimcdevitt@users.noreply.github.com> Date: Mon, 21 Oct 2024 11:24:54 -0700 Subject: [PATCH 41/53] Update docs/content/en/docs/clustermgmt/nodes/vmotion.md Co-authored-by: Chris Negus --- docs/content/en/docs/clustermgmt/nodes/vmotion.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/en/docs/clustermgmt/nodes/vmotion.md b/docs/content/en/docs/clustermgmt/nodes/vmotion.md index 7d4274258309..3bcd3ccc4e18 100755 --- a/docs/content/en/docs/clustermgmt/nodes/vmotion.md +++ b/docs/content/en/docs/clustermgmt/nodes/vmotion.md @@ -64,7 +64,7 @@ EKS Anywhere nodes cannot be migrated between different vCenter environments usi Shared storage is a requirement for vmotion of EKS-A clusters. Storage such as vSAN, Fiber Channel SAN, or NFS should be shared between the supporting vSphere ESXi hosts for maintaining access to the VM's backing data without relying on storage vMotion, which is not supported in EKS-A environments. -3. **Monitoring Before and After Migration** +* **Monitoring before and after migration** To verify cluster health and node stability, monitor the EKS-A nodes and pods before and after the vMotion migration: From 26a6f4f6928cb1170331ae0981128838feffee86 Mon Sep 17 00:00:00 2001 From: Mike McDevitt <117493168+mimcdevitt@users.noreply.github.com> Date: Mon, 21 Oct 2024 11:28:12 -0700 Subject: [PATCH 42/53] Update docs/content/en/docs/clustermgmt/nodes/vmotion.md Co-authored-by: Chris Negus --- docs/content/en/docs/clustermgmt/nodes/vmotion.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/en/docs/clustermgmt/nodes/vmotion.md b/docs/content/en/docs/clustermgmt/nodes/vmotion.md index 3bcd3ccc4e18..d9ee523ae1ea 100755 --- a/docs/content/en/docs/clustermgmt/nodes/vmotion.md +++ b/docs/content/en/docs/clustermgmt/nodes/vmotion.md @@ -66,7 +66,7 @@ EKS Anywhere nodes cannot be migrated between different vCenter environments usi * **Monitoring before and after migration** -To verify cluster health and node stability, monitor the EKS-A nodes and pods before and after the vMotion migration: + To verify cluster health and node stability, monitor the EKS-A nodes and pods before and after the vMotion migration: * Before migration, run the following commands to check the current health and status of the EKS-A nodes and pods. From 1f2c3a3d133d3dd9d25b8d9478738a10124804a8 Mon Sep 17 00:00:00 2001 From: Mike McDevitt <117493168+mimcdevitt@users.noreply.github.com> Date: Mon, 21 Oct 2024 11:28:27 -0700 Subject: [PATCH 43/53] Update docs/content/en/docs/clustermgmt/nodes/vmotion.md Co-authored-by: Chris Negus --- docs/content/en/docs/clustermgmt/nodes/vmotion.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/en/docs/clustermgmt/nodes/vmotion.md b/docs/content/en/docs/clustermgmt/nodes/vmotion.md index d9ee523ae1ea..d51625c0566e 100755 --- a/docs/content/en/docs/clustermgmt/nodes/vmotion.md +++ b/docs/content/en/docs/clustermgmt/nodes/vmotion.md @@ -68,7 +68,7 @@ EKS Anywhere nodes cannot be migrated between different vCenter environments usi To verify cluster health and node stability, monitor the EKS-A nodes and pods before and after the vMotion migration: -* Before migration, run the following commands to check the current health and status of the EKS-A nodes and pods. + * Before migration, run the following commands to check the current health and status of the EKS-A nodes and pods. ``` kubectl get nodes From 65706149227463ae17df02b310898ef466368836 Mon Sep 17 00:00:00 2001 From: Mike McDevitt <117493168+mimcdevitt@users.noreply.github.com> Date: Mon, 21 Oct 2024 11:28:37 -0700 Subject: [PATCH 44/53] Update docs/content/en/docs/clustermgmt/nodes/vmotion.md Co-authored-by: Chris Negus --- docs/content/en/docs/clustermgmt/nodes/vmotion.md | 1 - 1 file changed, 1 deletion(-) diff --git a/docs/content/en/docs/clustermgmt/nodes/vmotion.md b/docs/content/en/docs/clustermgmt/nodes/vmotion.md index d51625c0566e..353528042bd3 100755 --- a/docs/content/en/docs/clustermgmt/nodes/vmotion.md +++ b/docs/content/en/docs/clustermgmt/nodes/vmotion.md @@ -70,7 +70,6 @@ EKS Anywhere nodes cannot be migrated between different vCenter environments usi * Before migration, run the following commands to check the current health and status of the EKS-A nodes and pods. -``` kubectl get nodes kubectl get pods -a ``` From 6f3ee0ba0d86368d847b28588e421fb605942653 Mon Sep 17 00:00:00 2001 From: Mike McDevitt Date: Tue, 22 Oct 2024 11:28:34 -0700 Subject: [PATCH 45/53] Updating vmotion to VMotion and fixing code bock formating --- docs/content/en/docs/clustermgmt/nodes/vmotion.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/content/en/docs/clustermgmt/nodes/vmotion.md b/docs/content/en/docs/clustermgmt/nodes/vmotion.md index 353528042bd3..2dfb52e4aee0 100755 --- a/docs/content/en/docs/clustermgmt/nodes/vmotion.md +++ b/docs/content/en/docs/clustermgmt/nodes/vmotion.md @@ -45,7 +45,7 @@ EKS Anywhere nodes cannot be migrated between different vCenter environments usi * **EKS Anywhere configuration stabiltiy** - The EKS Anywhere environment itself should remain unchanged during vmotion. Do not perform or trigger any EKS Anywhere changes or life cycle events while performing vmotion. + The EKS Anywhere environment itself should remain unchanged during vMotion. Do not perform or trigger any EKS Anywhere changes or life cycle events while performing vmotion. ### Best practices for vMotion with EKS Anywhere clusters @@ -69,12 +69,13 @@ EKS Anywhere nodes cannot be migrated between different vCenter environments usi To verify cluster health and node stability, monitor the EKS-A nodes and pods before and after the vMotion migration: * Before migration, run the following commands to check the current health and status of the EKS-A nodes and pods. + * After vMotion activity is completed, run the commands again to verify that the nodes and pods are still operational and healthy. +``` kubectl get nodes kubectl get pods -a ``` - * After vMotion activity is completed, run the command again to verify that the nodes and pods are still operational and healthy. * **Infrastructure maintenance during vMotion** From 6cb5f77eef29a3ea0af75cec536781c6baeff524 Mon Sep 17 00:00:00 2001 From: Mike McDevitt <117493168+mimcdevitt@users.noreply.github.com> Date: Tue, 22 Oct 2024 14:03:43 -0700 Subject: [PATCH 46/53] Update docs/content/en/docs/clustermgmt/nodes/vmotion.md Co-authored-by: Chris Negus --- docs/content/en/docs/clustermgmt/nodes/vmotion.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/en/docs/clustermgmt/nodes/vmotion.md b/docs/content/en/docs/clustermgmt/nodes/vmotion.md index 2dfb52e4aee0..76004c098a42 100755 --- a/docs/content/en/docs/clustermgmt/nodes/vmotion.md +++ b/docs/content/en/docs/clustermgmt/nodes/vmotion.md @@ -19,7 +19,7 @@ When migrating EKS Anywhere nodes with vMotion, several considerations must be k * **No cross-vCenter vMotion** -EKS Anywhere nodes cannot be migrated between different vCenter environments using vMotion. The nodes must remain within the same vCenter instance for proper EKS Anywhere operation. The vCenter Server managing the EKS Anywhere cluster is specified in the `VSphereDatacenterConfig` section of the EKS Anywhere [vSphere cluster spec file]({{< relref "/docs/getting-started/vsphere/vsphere-spec" >}}), under the `spec.server` field, and cannot be changed. + EKS Anywhere nodes cannot be migrated between different vCenter environments using vMotion. The nodes must remain within the same vCenter instance for proper EKS Anywhere operation. The vCenter Server managing the EKS Anywhere cluster is specified in the `VSphereDatacenterConfig` section of the EKS Anywhere [vSphere cluster spec file]({{< relref "/docs/getting-started/vsphere/vsphere-spec" >}}), under the `spec.server` field, and cannot be changed. * **vSphere infrastructure settings in** `VSphereDatacenterConfig` From 34a2c9dac1a27b6b0988c3d672f30b5e1b0290c5 Mon Sep 17 00:00:00 2001 From: Mike McDevitt <117493168+mimcdevitt@users.noreply.github.com> Date: Tue, 22 Oct 2024 14:03:58 -0700 Subject: [PATCH 47/53] Update docs/content/en/docs/clustermgmt/nodes/vmotion.md Co-authored-by: Chris Negus --- docs/content/en/docs/clustermgmt/nodes/vmotion.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/en/docs/clustermgmt/nodes/vmotion.md b/docs/content/en/docs/clustermgmt/nodes/vmotion.md index 76004c098a42..3deb68351445 100755 --- a/docs/content/en/docs/clustermgmt/nodes/vmotion.md +++ b/docs/content/en/docs/clustermgmt/nodes/vmotion.md @@ -56,7 +56,7 @@ When migrating EKS Anywhere nodes with vMotion, several considerations must be k * VMware vMotion Networking Best Practices: Whenever possible, follow the [Networking Best Practices for VMware vMotion](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vcenterhost.doc/GUID-7DAD15D4-7F41-4913-9F16-567289E22977.html) to optimize performance and reduce the risk of issues during the migration process. - * Use High-Speed Networks: A 10GbE or higher speed network is recommended to ensure smooth vMotion operations for EKS-A nodes, particularly those with large memory footprints. + * Use High-Speed Networks: A 10GbE or higher speed network is recommended to ensure smooth vMotion operations for EKS Anywhere nodes, particularly those with large memory footprints. * **Shared Storage** From 8d4fe41ff5b9e76117d74abe87a43ae8a9a76917 Mon Sep 17 00:00:00 2001 From: Mike McDevitt <117493168+mimcdevitt@users.noreply.github.com> Date: Tue, 22 Oct 2024 14:04:05 -0700 Subject: [PATCH 48/53] Update docs/content/en/docs/clustermgmt/nodes/vmotion.md Co-authored-by: Chris Negus --- docs/content/en/docs/clustermgmt/nodes/vmotion.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/en/docs/clustermgmt/nodes/vmotion.md b/docs/content/en/docs/clustermgmt/nodes/vmotion.md index 3deb68351445..a86c031e2c9c 100755 --- a/docs/content/en/docs/clustermgmt/nodes/vmotion.md +++ b/docs/content/en/docs/clustermgmt/nodes/vmotion.md @@ -66,7 +66,7 @@ When migrating EKS Anywhere nodes with vMotion, several considerations must be k * **Monitoring before and after migration** - To verify cluster health and node stability, monitor the EKS-A nodes and pods before and after the vMotion migration: + To verify cluster health and node stability, monitor the EKS Anywhere nodes and pods before and after the vMotion migration: * Before migration, run the following commands to check the current health and status of the EKS-A nodes and pods. * After vMotion activity is completed, run the commands again to verify that the nodes and pods are still operational and healthy. From 97fec9f69b4231a7d49ea4a57defcaeb854786b3 Mon Sep 17 00:00:00 2001 From: Mike McDevitt <117493168+mimcdevitt@users.noreply.github.com> Date: Tue, 22 Oct 2024 14:04:40 -0700 Subject: [PATCH 49/53] Update docs/content/en/docs/clustermgmt/nodes/vmotion.md Co-authored-by: Chris Negus --- docs/content/en/docs/clustermgmt/nodes/vmotion.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/en/docs/clustermgmt/nodes/vmotion.md b/docs/content/en/docs/clustermgmt/nodes/vmotion.md index a86c031e2c9c..8434e8e5ca99 100755 --- a/docs/content/en/docs/clustermgmt/nodes/vmotion.md +++ b/docs/content/en/docs/clustermgmt/nodes/vmotion.md @@ -68,7 +68,7 @@ When migrating EKS Anywhere nodes with vMotion, several considerations must be k To verify cluster health and node stability, monitor the EKS Anywhere nodes and pods before and after the vMotion migration: - * Before migration, run the following commands to check the current health and status of the EKS-A nodes and pods. + * Before migration, run the following commands to check the current health and status of the EKS Anywhere nodes and pods. * After vMotion activity is completed, run the commands again to verify that the nodes and pods are still operational and healthy. ``` From e36e840ac2814f3a44132f7d2773d2198a591ab3 Mon Sep 17 00:00:00 2001 From: Mike McDevitt <117493168+mimcdevitt@users.noreply.github.com> Date: Tue, 22 Oct 2024 14:04:51 -0700 Subject: [PATCH 50/53] Update docs/content/en/docs/clustermgmt/nodes/vmotion.md Co-authored-by: Chris Negus --- docs/content/en/docs/clustermgmt/nodes/vmotion.md | 1 - 1 file changed, 1 deletion(-) diff --git a/docs/content/en/docs/clustermgmt/nodes/vmotion.md b/docs/content/en/docs/clustermgmt/nodes/vmotion.md index 8434e8e5ca99..a2fb78f70f41 100755 --- a/docs/content/en/docs/clustermgmt/nodes/vmotion.md +++ b/docs/content/en/docs/clustermgmt/nodes/vmotion.md @@ -71,7 +71,6 @@ When migrating EKS Anywhere nodes with vMotion, several considerations must be k * Before migration, run the following commands to check the current health and status of the EKS Anywhere nodes and pods. * After vMotion activity is completed, run the commands again to verify that the nodes and pods are still operational and healthy. -``` kubectl get nodes kubectl get pods -a ``` From 1b15b793d9508379c0bec432d080b9aa958573df Mon Sep 17 00:00:00 2001 From: Mike McDevitt <117493168+mimcdevitt@users.noreply.github.com> Date: Tue, 22 Oct 2024 14:04:59 -0700 Subject: [PATCH 51/53] Update docs/content/en/docs/clustermgmt/nodes/vmotion.md Co-authored-by: Chris Negus --- docs/content/en/docs/clustermgmt/nodes/vmotion.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/en/docs/clustermgmt/nodes/vmotion.md b/docs/content/en/docs/clustermgmt/nodes/vmotion.md index a2fb78f70f41..9497cebb7195 100755 --- a/docs/content/en/docs/clustermgmt/nodes/vmotion.md +++ b/docs/content/en/docs/clustermgmt/nodes/vmotion.md @@ -61,7 +61,7 @@ When migrating EKS Anywhere nodes with vMotion, several considerations must be k * **Shared Storage** - Shared storage is a requirement for vmotion of EKS-A clusters. Storage such as vSAN, Fiber Channel SAN, or NFS should be shared between the supporting vSphere ESXi hosts for maintaining access to the VM's backing data without relying on storage vMotion, which is not supported in EKS-A environments. + Shared storage is a requirement for vmotion of EKS Anywhere clusters. Storage such as vSAN, Fiber Channel SAN, or NFS should be shared between the supporting vSphere ESXi hosts for maintaining access to the VM's backing data without relying on storage vMotion, which is not supported in EKS Anywhere environments. * **Monitoring before and after migration** From a39b2d8c6ce64ce155eca701e9eb5f0e4abe2391 Mon Sep 17 00:00:00 2001 From: Mike McDevitt <117493168+mimcdevitt@users.noreply.github.com> Date: Tue, 22 Oct 2024 14:05:06 -0700 Subject: [PATCH 52/53] Update docs/content/en/docs/clustermgmt/nodes/vmotion.md Co-authored-by: Chris Negus --- docs/content/en/docs/clustermgmt/nodes/vmotion.md | 1 - 1 file changed, 1 deletion(-) diff --git a/docs/content/en/docs/clustermgmt/nodes/vmotion.md b/docs/content/en/docs/clustermgmt/nodes/vmotion.md index 9497cebb7195..c9cb39137b7a 100755 --- a/docs/content/en/docs/clustermgmt/nodes/vmotion.md +++ b/docs/content/en/docs/clustermgmt/nodes/vmotion.md @@ -73,7 +73,6 @@ When migrating EKS Anywhere nodes with vMotion, several considerations must be k kubectl get nodes kubectl get pods -a -``` From 80d135739fe7b5df177d403e961d64c6249ba84b Mon Sep 17 00:00:00 2001 From: Mike McDevitt Date: Wed, 23 Oct 2024 01:41:04 -0700 Subject: [PATCH 53/53] restore formatting of kubectl commands section --- docs/content/en/docs/clustermgmt/nodes/vmotion.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/content/en/docs/clustermgmt/nodes/vmotion.md b/docs/content/en/docs/clustermgmt/nodes/vmotion.md index c9cb39137b7a..72ea8eb58be9 100755 --- a/docs/content/en/docs/clustermgmt/nodes/vmotion.md +++ b/docs/content/en/docs/clustermgmt/nodes/vmotion.md @@ -71,9 +71,11 @@ When migrating EKS Anywhere nodes with vMotion, several considerations must be k * Before migration, run the following commands to check the current health and status of the EKS Anywhere nodes and pods. * After vMotion activity is completed, run the commands again to verify that the nodes and pods are still operational and healthy. + +``` kubectl get nodes kubectl get pods -a - +``` * **Infrastructure maintenance during vMotion**