Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Merged
merged 1 commit into from
Jan 9, 2025
Merged

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

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion docs/rancher/node/k3s-cluster.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 involves configuring the IP address of the underlying virtual machines. You can do this using a DHCP server on the VLAN network that the virtual machines are attached to. If such a server does not exist on the network, you can use the [Managed DHCP](../../advanced/addons/managed-dhcp.md) feature to configure the IP address.
- [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).
Expand Down Expand Up @@ -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
```
```
1 change: 1 addition & 0 deletions docs/rancher/node/rke1-cluster.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 involves configuring the IP address of the underlying virtual machines. You can do this using a DHCP server on the VLAN network that the virtual machines are attached to. If such a server does not exist on the network, you can use the [Managed DHCP](../../advanced/addons/managed-dhcp.md) feature to configure the IP address.
- 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).

Expand Down
1 change: 1 addition & 0 deletions docs/rancher/node/rke2-cluster.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 involves configuring the IP address of the underlying virtual machines. You can do this using a DHCP server on the VLAN network that the virtual machines are attached to. If such a server does not exist on the network, you can use the [Managed DHCP](../../advanced/addons/managed-dhcp.md) feature to configure the IP address.
- 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/).
Expand Down
3 changes: 2 additions & 1 deletion versioned_docs/version-v1.3/rancher/node/k3s-cluster.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 involves configuring the IP address of the underlying virtual machines. You can do this using a DHCP server on the VLAN network that the virtual machines are attached to. If such a server does not exist on the network, you can use the [Managed DHCP](../../advanced/addons/managed-dhcp.md) feature to configure the IP address.
- 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).

Expand Down Expand Up @@ -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
```
```
1 change: 1 addition & 0 deletions versioned_docs/version-v1.3/rancher/node/rke1-cluster.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 involves configuring the IP address of the underlying virtual machines. You can do this using a DHCP server on the VLAN network that the virtual machines are attached to. If such a server does not exist on the network, you can use the [Managed DHCP](../../advanced/addons/managed-dhcp.md) feature to configure the IP address.
- 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).

Expand Down
1 change: 1 addition & 0 deletions versioned_docs/version-v1.3/rancher/node/rke2-cluster.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 involves configuring the IP address of the underlying virtual machines. You can do this using a DHCP server on the VLAN network that the virtual machines are attached to. If such a server does not exist on the network, you can use the [Managed DHCP](../../advanced/addons/managed-dhcp.md) feature to configure the IP address.
- 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/).
Expand Down
3 changes: 2 additions & 1 deletion versioned_docs/version-v1.4/rancher/node/k3s-cluster.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 involves configuring the IP address of the underlying virtual machines. You can do this using a DHCP server on the VLAN network that the virtual machines are attached to. If such a server does not exist on the network, you can use the [Managed DHCP](../../advanced/addons/managed-dhcp.md) feature to configure the IP address.
- 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).

Expand Down Expand Up @@ -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
```
```
1 change: 1 addition & 0 deletions versioned_docs/version-v1.4/rancher/node/rke1-cluster.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 involves configuring the IP address of the underlying virtual machines. You can do this using a DHCP server on the VLAN network that the virtual machines are attached to. If such a server does not exist on the network, you can use the [Managed DHCP](../../advanced/addons/managed-dhcp.md) feature to configure the IP address.
- 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).

Expand Down
1 change: 1 addition & 0 deletions versioned_docs/version-v1.4/rancher/node/rke2-cluster.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 involves configuring the IP address of the underlying virtual machines. You can do this using a DHCP server on the VLAN network that the virtual machines are attached to. If such a server does not exist on the network, you can use the [Managed DHCP](../../advanced/addons/managed-dhcp.md) feature to configure the IP address.
- 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/).
Expand Down
Loading