Creating an RKE2 Kubernetes Cluster
Users can now provision RKE2 Kubernetes clusters on top of the Harvester cluster in Rancher v2.6.1+
using the built-in Harvester node driver.
- Harvester RKE2 node driver is in tech preview.
- VLAN network is required for Harvester node driver.
Create Your Cloud Credentials
- Click ☰ > Cluster Management.
- Click Cloud Credentials.
- Click Create.
- Click Harvester.
- Enter your cloud credential name
- Select "Imported Harvester" or "External Harvester".
- Click Create.
Create RKE2 Kubernetes Cluster
Users can create a RKE2 Kubernetes cluster from the Cluster Management page via the RKE2 node driver.
- Select Clusters menu.
- Click Create button.
- Toggle Switch to RKE2/K3s.
- Select Harvester node driver.
- Select a Cloud Credential.
- Enter Cluster Name (required).
- Enter Namespace (required).
- Enter Image (required).
- Enter Network Name (required).
- Enter SSH User (required).
- Click Create.
- RKE2 v1.21.5+rke2r2 or above provides a built-in Harvester Cloud Provider and Guest CSI driver integration.
- Currently only imported Harvester clusters are supported automatically.
Add Node Affinity
Available as of v1.0.3 + Rancher v2.6.7
The Harvester node driver now supports scheduling a group of machines to particular nodes through the node affinity rules, which can provide high availability and better resource utilization.
Node affinity can be added to the machine pools during the cluster creation:
- Click the
Show Advanced
button and click theAdd Node Selector
- Set priority to
Required
if you wish the scheduler to schedule the machines only when the rules are met. - Click
Add Rule
to specify the node affinity rules, e.g., for the topology spread constraints use case, you can add theregion
andzone
labels as follows:key: topology.kubernetes.io/region
operator: in list
values: us-east-1
---
key: topology.kubernetes.io/zone
operator: in list
values: us-east-1a - Click
Create
to save the node template. After the cluster is installed, you can check whether its machine nodes are scheduled accordingly to the affinity rules.
Using Harvester RKE2 Node Driver in Air Gapped Environment
RKE2 provisioning relies on the qemu-guest-agent
to get the IP of the virtual machine. However, it may not be feasible to install qemu-guest-agent
in an air gapped environment.
You can address the installation constraints with the following options:
Option 1. Use a VM image with qemu-guest-agent
installed.
Option 2. Configure the cloud init
user data to enable the VMs to install qemu-guest-agent
via an HTTP(S) proxy.
Example user data in Harvester node template:
#cloud-config
apt:
http_proxy: http://192.168.0.1:3128
https_proxy: http://192.168.0.1:3128