doc(rancher): suggest managed dhcp for creating guest cluster

Signed-off-by: Zespre Chang <[email protected]>
harvester · Jan 7, 2025 · 64fcdf3 · 64fcdf3
1 parent 1a4478c
commit 64fcdf3
Show file tree

Hide file tree

Showing 9 changed files with 12 additions and 3 deletions.
diff --git a/docs/rancher/node/k3s-cluster.md b/docs/rancher/node/k3s-cluster.md
@@ -15,6 +15,7 @@ You can now provision K3s Kubernetes clusters on top of the Harvester cluster in
 :::note
 
 - Harvester K3s node driver is in **Tech Preview**.
+- Provisioning K3s Kubernetes clusters requires a means to configure the IP address of the underlying virtual machines. A typical way is to use DHCP. If you don't have an existing DHCP server on the VLAN network where the virtual machines are attached to, or you don't bother to spin up a new DHCP server, you can use the [Managed DHCP](../../advanced/addons/managed-dhcp.md) feature to achieve the same goal.
 - [VLAN network](../../networking/harvester-network.md#vlan-network) is required for Harvester node driver.
 - Harvester node driver only supports cloud images.
 - For the port requirements of the guest clusters deployed within Harvester, please refer to the [port requirements for guest clusters](../../install/requirements.md#port-requirements-for-k3s-or-rkerke2-clusters).
@@ -93,4 +94,4 @@ Example of `user data` in Harvester node template:
 apt:
   http_proxy: http://192.168.0.1:3128
   https_proxy: http://192.168.0.1:3128
-```
+```
diff --git a/docs/rancher/node/rke1-cluster.md b/docs/rancher/node/rke1-cluster.md
@@ -17,6 +17,7 @@ RKE1 and RKE2 have several slight behavioral differences. Refer to the [differen
 :::note
 
 - VLAN network is required for Harvester node driver.
+- Provisioning RKE1 Kubernetes clusters requires a means to configure the IP address of the underlying virtual machines. A typical way is to use DHCP. If you don't have an existing DHCP server on the VLAN network where the virtual machines are attached to, or you don't bother to spin up a new DHCP server, you can use the [Managed DHCP](../../advanced/addons/managed-dhcp.md) feature to achieve the same goal.
 - Harvester node driver only supports cloud images.
 - For port requirements of guest clusters deployed within Harvester, please refer to the [port requirements for guest clusters](../../install/requirements.md#port-requirements-for-k3s-or-rkerke2-clusters).
 

diff --git a/docs/rancher/node/rke2-cluster.md b/docs/rancher/node/rke2-cluster.md
@@ -15,6 +15,7 @@ You can now provision RKE2 Kubernetes clusters on top of the Harvester cluster i
 :::note
 
 - [VLAN network](../../networking/harvester-network.md#vlan-network) is required for Harvester node driver.
+- Provisioning RKE2 Kubernetes clusters requires a means to configure the IP address of the underlying virtual machines. A typical way is to use DHCP. If you don't have an existing DHCP server on the VLAN network where the virtual machines are attached to, or you don't bother to spin up a new DHCP server, you can use the [Managed DHCP](../../advanced/addons/managed-dhcp.md) feature to achieve the same goal.
 - Harvester node driver only supports cloud images.
 - For the port requirements of the guest clusters deployed within Harvester, please refer to the doc [here](../../install/requirements.md#port-requirements-for-k3s-or-rkerke2-clusters).
 - For RKE2 with Harvester cloud provider support matrix, please refer to the website [here](https://www.suse.com/suse-harvester/support-matrix/all-supported-versions/).

diff --git a/versioned_docs/version-v1.3/rancher/node/k3s-cluster.md b/versioned_docs/version-v1.3/rancher/node/k3s-cluster.md
@@ -16,6 +16,7 @@ You can now provision K3s Kubernetes clusters on top of the Harvester cluster in
 
 - Harvester K3s node driver is in **Tech Preview**.
 - [VLAN network](../../networking/harvester-network.md#vlan-network) is required for Harvester node driver.
+- Provisioning K3s Kubernetes clusters requires a means to configure the IP address of the underlying virtual machines. A typical way is to use DHCP. If you don't have an existing DHCP server on the VLAN network where the virtual machines are attached to, or you don't bother to spin up a new DHCP server, you can use the [Managed DHCP](../../advanced/addons/managed-dhcp.md) feature to achieve the same goal.
 - Harvester node driver only supports cloud images.
 - For the port requirements of the guest clusters deployed within Harvester, please refer to the [port requirements for guest clusters](../../install/requirements.md#port-requirements-for-k3s-or-rkerke2-clusters).
 
@@ -93,4 +94,4 @@ Example of `user data` in Harvester node template:
 apt:
   http_proxy: http://192.168.0.1:3128
   https_proxy: http://192.168.0.1:3128
-```
+```
diff --git a/versioned_docs/version-v1.3/rancher/node/rke1-cluster.md b/versioned_docs/version-v1.3/rancher/node/rke1-cluster.md
@@ -17,6 +17,7 @@ RKE1 and RKE2 have several slight behavioral differences. Refer to the [differen
 :::note
 
 - VLAN network is required for Harvester node driver.
+- Provisioning RKE1 Kubernetes clusters requires a means to configure the IP address of the underlying virtual machines. A typical way is to use DHCP. If you don't have an existing DHCP server on the VLAN network where the virtual machines are attached to, or you don't bother to spin up a new DHCP server, you can use the [Managed DHCP](../../advanced/addons/managed-dhcp.md) feature to achieve the same goal.
 - Harvester node driver only supports cloud images.
 - For port requirements of guest clusters deployed within Harvester, please refer to the [port requirements for guest clusters](../../install/requirements.md#port-requirements-for-k3s-or-rkerke2-clusters).
 

diff --git a/versioned_docs/version-v1.3/rancher/node/rke2-cluster.md b/versioned_docs/version-v1.3/rancher/node/rke2-cluster.md
@@ -15,6 +15,7 @@ You can now provision RKE2 Kubernetes clusters on top of the Harvester cluster i
 :::note
 
 - [VLAN network](../../networking/harvester-network.md#vlan-network) is required for Harvester node driver.
+- Provisioning RKE2 Kubernetes clusters requires a means to configure the IP address of the underlying virtual machines. A typical way is to use DHCP. If you don't have an existing DHCP server on the VLAN network where the virtual machines are attached to, or you don't bother to spin up a new DHCP server, you can use the [Managed DHCP](../../advanced/addons/managed-dhcp.md) feature to achieve the same goal.
 - Harvester node driver only supports cloud images.
 - For the port requirements of the guest clusters deployed within Harvester, please refer to the doc [here](../../install/requirements.md#port-requirements-for-k3s-or-rkerke2-clusters).
 - For RKE2 with Harvester cloud provider support matrix, please refer to the website [here](https://www.suse.com/suse-harvester/support-matrix/all-supported-versions/).

diff --git a/versioned_docs/version-v1.4/rancher/node/k3s-cluster.md b/versioned_docs/version-v1.4/rancher/node/k3s-cluster.md
@@ -16,6 +16,7 @@ You can now provision K3s Kubernetes clusters on top of the Harvester cluster in
 
 - Harvester K3s node driver is in **Tech Preview**.
 - [VLAN network](../../networking/harvester-network.md#vlan-network) is required for Harvester node driver.
+- Provisioning K3s Kubernetes clusters requires a means to configure the IP address of the underlying virtual machines. A typical way is to use DHCP. If you don't have an existing DHCP server on the VLAN network where the virtual machines are attached to, or you don't bother to spin up a new DHCP server, you can use the [Managed DHCP](../../advanced/addons/managed-dhcp.md) feature to achieve the same goal.
 - Harvester node driver only supports cloud images.
 - For the port requirements of the guest clusters deployed within Harvester, please refer to the [port requirements for guest clusters](../../install/requirements.md#port-requirements-for-k3s-or-rkerke2-clusters).
 
@@ -93,4 +94,4 @@ Example of `user data` in Harvester node template:
 apt:
   http_proxy: http://192.168.0.1:3128
   https_proxy: http://192.168.0.1:3128
-```
+```
diff --git a/versioned_docs/version-v1.4/rancher/node/rke1-cluster.md b/versioned_docs/version-v1.4/rancher/node/rke1-cluster.md
@@ -17,6 +17,7 @@ RKE1 and RKE2 have several slight behavioral differences. Refer to the [differen
 :::note
 
 - VLAN network is required for Harvester node driver.
+- Provisioning RKE1 Kubernetes clusters requires a means to configure the IP address of the underlying virtual machines. A typical way is to use DHCP. If you don't have an existing DHCP server on the VLAN network where the virtual machines are attached to, or you don't bother to spin up a new DHCP server, you can use the [Managed DHCP](../../advanced/addons/managed-dhcp.md) feature to achieve the same goal.
 - Harvester node driver only supports cloud images.
 - For port requirements of guest clusters deployed within Harvester, please refer to the [port requirements for guest clusters](../../install/requirements.md#port-requirements-for-k3s-or-rkerke2-clusters).
 

diff --git a/versioned_docs/version-v1.4/rancher/node/rke2-cluster.md b/versioned_docs/version-v1.4/rancher/node/rke2-cluster.md
@@ -15,6 +15,7 @@ You can now provision RKE2 Kubernetes clusters on top of the Harvester cluster i
 :::note
 
 - [VLAN network](../../networking/harvester-network.md#vlan-network) is required for Harvester node driver.
+- Provisioning RKE2 Kubernetes clusters requires a means to configure the IP address of the underlying virtual machines. A typical way is to use DHCP. If you don't have an existing DHCP server on the VLAN network where the virtual machines are attached to, or you don't bother to spin up a new DHCP server, you can use the [Managed DHCP](../../advanced/addons/managed-dhcp.md) feature to achieve the same goal.
 - Harvester node driver only supports cloud images.
 - For the port requirements of the guest clusters deployed within Harvester, please refer to the doc [here](../../install/requirements.md#port-requirements-for-k3s-or-rkerke2-clusters).
 - For RKE2 with Harvester cloud provider support matrix, please refer to the website [here](https://www.suse.com/suse-harvester/support-matrix/all-supported-versions/).