Apply requested doc updates (#768)

* Change supported to validated in guest OS section
Signed-off-by: Jillian <[email protected]>

* Add maximum vCPU count
Signed-off-by: Jillian <[email protected]>

* Add note regarding RKE EOL
Signed-off-by: Jillian <[email protected]>

---------
Signed-off-by: Jillian <[email protected]>

Author: jillian-maroket

docs/rancher/rancher-integration.md

@@ -66,7 +66,13 @@ For in-depth insights, please refer to the [virtualization management](./virtual
 
 ## Creating Kubernetes clusters using the Harvester node driver
 
-You can launch a Kubernetes cluster from Rancher using the [Harvester node driver](./node/node-driver.md). When Rancher deploys Kubernetes onto these nodes, you can choose between Rancher Kubernetes Engine (RKE) or RKE2 distributions.
+You can launch a Kubernetes cluster from Rancher using the [Harvester node driver](./node/node-driver.md). When Rancher deploys Kubernetes onto these nodes, choose RKE2.
+
+:::note
+
+Rancher Kubernetes Engine (RKE) will reach the end of its life on **July 31, 2025**. Harvester **v1.6.0** and later versions will not support RKE. Using RKE2, which provides a more secure and efficient environment, is recommended.
+
+:::
 
 One benefit of installing Kubernetes on node pools hosted by the node driver is that if a node loses connectivity with the cluster, Rancher can automatically create another node to join the cluster to ensure that the count of the node pool is as expected.
 

docs/vm/create-vm.md

@@ -35,8 +35,9 @@ Please refer to [this page](./create-windows-vm.md) for creating Windows virtual
 1. Select the namespace of your VMs, only the `harvester-public` namespace is visible to all users.
 1. The VM Name is a required field.
 1. (Optional) VM template is optional, you can choose `iso-image`, `raw-image` or `windows-iso-image` template to speed up your VM instance creation.
-1. Configure the virtual machine's CPU and memory (see [overcommit settings](../advanced/settings.md#overcommit-config) if you want to over-provision).
-1. Select SSH keys or upload new keys.
+1. On the **Basics** tab, configure the following settings:
+  - **CPU** and **Memory**: You can allocate a maximum of **254** vCPUs. If virtual machines are not expected to fully consume the allocated resources most of the time, you can use the [`overcommit-config`](../advanced/settings.md#overcommit-config) setting to optimize physical resource allocation.
+  - **SSHKey**: Select SSH keys or upload new keys.
 1. Select a custom VM image on the **Volumes** tab. The default disk will be the root disk. You can add more disks to the VM.
 1. To configure networks, go to the **Networks** tab. 
     1. The **Management Network** is added by default, you can remove it if the VLAN network is configured.

docs/vm/virtual-machines.md

@@ -22,7 +22,7 @@ You can create [Linux VMs](../vm/create-vm.md) using one of the following method
 
 Creating [Windows VMs](../vm/create-windows-vm.md) on the Harvester UI involves slightly different steps. Harvester provides a VM template named `windows-iso-image-base-template` that adds a volume with the Virtio drivers for Windows, which streamlines the VM configuration process. If you require Virtio devices but choose to not use the template, you must add your own Virtio drivers for Windows to enable correct hardware detection. 
 
-## Supported Guest Operating Systems
+## Validated Guest Operating Systems
 
 The following operating systems have been validated to run in Harvester virtual machines:
 

versioned_docs/version-v1.3/rancher/rancher-integration.md

@@ -66,7 +66,13 @@ For in-depth insights, please refer to the [virtualization management](./virtual
 
 ## Creating Kubernetes clusters using the Harvester node driver
 
-You can launch a Kubernetes cluster from Rancher using the [Harvester node driver](./node/node-driver.md). When Rancher deploys Kubernetes onto these nodes, you can choose between Rancher Kubernetes Engine (RKE) or RKE2 distributions.
+You can launch a Kubernetes cluster from Rancher using the [Harvester node driver](./node/node-driver.md). When Rancher deploys Kubernetes onto these nodes, choose RKE2.
+
+:::note
+
+Rancher Kubernetes Engine (RKE) will reach the end of its life on **July 31, 2025**. Harvester **v1.6.0** and later versions will not support RKE. Using RKE2, which provides a more secure and efficient environment, is recommended.
+
+:::
 
 One benefit of installing Kubernetes on node pools hosted by the node driver is that if a node loses connectivity with the cluster, Rancher can automatically create another node to join the cluster to ensure that the count of the node pool is as expected.
 

versioned_docs/version-v1.3/vm/create-vm.md

@@ -32,8 +32,9 @@ Please refer to [this page](./create-windows-vm.md) for creating Windows virtual
 1. Select the namespace of your VMs, only the `harvester-public` namespace is visible to all users.
 1. The VM Name is a required field.
 1. (Optional) VM template is optional, you can choose `iso-image`, `raw-image` or `windows-iso-image` template to speed up your VM instance creation.
-1. Configure the virtual machine's CPU and memory (see [overcommit settings](../advanced/settings.md#overcommit-config) if you want to over-provision).
-1. Select SSH keys or upload new keys.
+1. On the **Basics** tab, configure the following settings:
+  - **CPU** and **Memory**: You can allocate a maximum of **254** vCPUs. If virtual machines are not expected to fully consume the allocated resources most of the time, you can use the [`overcommit-config`](../advanced/settings.md#overcommit-config) setting to optimize physical resource allocation.
+  - **SSHKey**: Select SSH keys or upload new keys.
 1. Select a custom VM image on the **Volumes** tab. The default disk will be the root disk. You can add more disks to the VM.
 1. To configure networks, go to the **Networks** tab. 
     1. The **Management Network** is added by default, you can remove it if the VLAN network is configured.

versioned_docs/version-v1.3/vm/virtual-machines.md

@@ -22,7 +22,7 @@ You can create [Linux VMs](../vm/create-vm.md) using one of the following method
 
 Creating [Windows VMs](../vm/create-windows-vm.md) on the Harvester UI involves slightly different steps. Harvester provides a VM template named `windows-iso-image-base-template` that adds a volume with the Virtio drivers for Windows, which streamlines the VM configuration process. If you require Virtio devices but choose to not use the template, you must add your own Virtio drivers for Windows to enable correct hardware detection. 
 
-## Supported Guest Operating Systems
+## Validated Guest Operating Systems
 
 The following operating systems have been validated to run in Harvester virtual machines:
 

versioned_docs/version-v1.4/rancher/rancher-integration.md

@@ -66,7 +66,13 @@ For in-depth insights, please refer to the [virtualization management](./virtual
 
 ## Creating Kubernetes clusters using the Harvester node driver
 
-You can launch a Kubernetes cluster from Rancher using the [Harvester node driver](./node/node-driver.md). When Rancher deploys Kubernetes onto these nodes, you can choose between Rancher Kubernetes Engine (RKE) or RKE2 distributions.
+You can launch a Kubernetes cluster from Rancher using the [Harvester node driver](./node/node-driver.md). When Rancher deploys Kubernetes onto these nodes, choose RKE2.
+
+:::note
+
+Rancher Kubernetes Engine (RKE) will reach the end of its life on **July 31, 2025**. Harvester **v1.6.0** and later versions will not support RKE. Using RKE2, which provides a more secure and efficient environment, is recommended.
+
+:::
 
 One benefit of installing Kubernetes on node pools hosted by the node driver is that if a node loses connectivity with the cluster, Rancher can automatically create another node to join the cluster to ensure that the count of the node pool is as expected.
 

versioned_docs/version-v1.4/vm/create-vm.md

@@ -35,8 +35,9 @@ Please refer to [this page](./create-windows-vm.md) for creating Windows virtual
 1. Select the namespace of your VMs, only the `harvester-public` namespace is visible to all users.
 1. The VM Name is a required field.
 1. (Optional) VM template is optional, you can choose `iso-image`, `raw-image` or `windows-iso-image` template to speed up your VM instance creation.
-1. Configure the virtual machine's CPU and memory (see [overcommit settings](../advanced/settings.md#overcommit-config) if you want to over-provision).
-1. Select SSH keys or upload new keys.
+1. On the **Basics** tab, configure the following settings:
+  - **CPU** and **Memory**: You can allocate a maximum of **254** vCPUs. If virtual machines are not expected to fully consume the allocated resources most of the time, you can use the [`overcommit-config`](../advanced/settings.md#overcommit-config) setting to optimize physical resource allocation.
+  - **SSHKey**: Select SSH keys or upload new keys.
 1. Select a custom VM image on the **Volumes** tab. The default disk will be the root disk. You can add more disks to the VM.
 1. To configure networks, go to the **Networks** tab. 
     1. The **Management Network** is added by default, you can remove it if the VLAN network is configured.

versioned_docs/version-v1.4/vm/virtual-machines.md

@@ -22,7 +22,7 @@ You can create [Linux VMs](../vm/create-vm.md) using one of the following method
 
 Creating [Windows VMs](../vm/create-windows-vm.md) on the Harvester UI involves slightly different steps. Harvester provides a VM template named `windows-iso-image-base-template` that adds a volume with the Virtio drivers for Windows, which streamlines the VM configuration process. If you require Virtio devices but choose to not use the template, you must add your own Virtio drivers for Windows to enable correct hardware detection. 
 
-## Supported Guest Operating Systems
+## Validated Guest Operating Systems
 
 The following operating systems have been validated to run in Harvester virtual machines:
 

versioned_docs/version-v1.5/rancher/rancher-integration.md

@@ -66,7 +66,13 @@ For in-depth insights, please refer to the [virtualization management](./virtual
 
 ## Creating Kubernetes clusters using the Harvester node driver
 
-You can launch a Kubernetes cluster from Rancher using the [Harvester node driver](./node/node-driver.md). When Rancher deploys Kubernetes onto these nodes, you can choose between Rancher Kubernetes Engine (RKE) or RKE2 distributions.
+You can launch a Kubernetes cluster from Rancher using the [Harvester node driver](./node/node-driver.md). When Rancher deploys Kubernetes onto these nodes, choose RKE2.
+
+:::note
+
+Rancher Kubernetes Engine (RKE) will reach the end of its life on **July 31, 2025**. Harvester **v1.6.0** and later versions will not support RKE. Using RKE2, which provides a more secure and efficient environment, is recommended.
+
+:::
 
 One benefit of installing Kubernetes on node pools hosted by the node driver is that if a node loses connectivity with the cluster, Rancher can automatically create another node to join the cluster to ensure that the count of the node pool is as expected.