I have finally added a third node to my Harvester v1.0.0 cluster. (I started with node 003, then added 002, and finally added 001 today). I thought that after adding the third node the cluster would turn into an HA cluster where all three nodes are the control plane with etcd, but that has not happened. Have I done something wrong?

$ kubectl get nodes -o wide --context harvester003
NAME           STATUS   ROLES                       AGE   VERSION          INTERNAL-IP   EXTERNAL-IP   OS-IMAGE           KERNEL-VERSION         CONTAINER-RUNTIME
harvester001   Ready    <none>                      29m   v1.21.7+rke2r1   10.64.0.16    <none>        Harvester v1.0.0   5.3.18-59.37-default   <containerd://1.4.12-k3s1>
harvester002   Ready    <none>                      63d   v1.21.7+rke2r1   10.64.0.17    <none>        Harvester v1.0.0   5.3.18-59.37-default   <containerd://1.4.12-k3s1>
harvester003   Ready    control-plane,etcd,master   84d   v1.21.7+rke2r1   10.64.0.18    <none>        Harvester v1.0.0   5.3.18-59.37-default   <containerd://1.4.12-k3s1>

Hey Can anyone help me troubleshoot this pod?

Is it possible to change the management nodes to different hosts?

Quick question: how do I restart the kubelet in harvester? When I describe the node, I see that kubelet has stopped posting status. Also, where are the kubelet logs?

I noticed that it's possible to rollout various ssh-keys to the Harvester nodes at installation time. To follow the normal lifecycle it is necessary to be able to add or remove keys later at runtime. How can this be achieved?

Can anyone clarify the best practice when you need both k8s and vms? Rancher helm chart on harvester's k8s? k3s with rancher in vms? Separate rancher for management on bare metal or vms? Just use harvester k8s?

Also what causes this

Has anyone had reliable success creating a VM from an ISO? I've been trying over and over to get something like Ubuntu desktop (both 22.04 and 20.04). I either get "starting" or on the off chance that it does start and I can go through the setup phase, it can't find the disk after the install and reboot. I've tried using the template and creating the VM from scratch.

Is it possible to create dual-stack rke2/k3s clusters using the harvester node driver on rancher?

is it true that minimal number of nodes in a HA cluster is 3 nodes? could we deploy new VMs on these 3 nodes, or these 3 nodes have to be k8s master nodes, and they could not be used for anything else (meaning running new user VMs)?

Trying to upload RHEL 8.5 to Harvester but fails. Is it to big of a file? iso is 10gb

The harvester vip pool load balancer; is it possible to get real client IPs delivered down to workloads while using this?

(I also have 2x 4 TB drives on each node, but those are supposed to be data drives...)

https://docs.harvesterhci.io/v1.0/dev/dev-mode/ I followed the documentation but failed. How to do it? Does the document need to be updated?

How to install harvester in k8s?

In page https://docs.harvesterhci.io/v1.0/upgrade/automatic/ , there are some warnings about shutting down the VMs while upgrading the Harvester. Does it mean that we really need to shut down all VMs on every host and keep them all down while upgrading Harvester (causing potential downtime in the environment)? Is it still the case for upgrading from 1.0.1 to a future version?

Hey all. Does an HA harvester run workloads on management nodes? Or are those sacrificed compute if too large?

Is anyone else experiencing "Failed to wait for processing start in 60 seconds" on image uploads? I have no issues creating images when using a URL, but they fail with uploads — regardless of which image (ISO) I choose. I'm not experiencing this on other hypervisors with the same images.

My lab environment does not have a DHCP server. I am trying to deploy it using the following link mentioned in the document. https://github.com/harvester/harvester/issues/947 but unable to do so. Anybody tried it. It would be helpful if I get to know what configuration needs to be changed in the above YAML to get it working. Thanks in advance

Hi, What is the latest version of Harvest at present? And when is the next release is scheduled to be released? I am still waiting for VXLAN support. Thank you.

I'm playing a bit with my harvester virtual box image. No customizations yet. Plain image with 2 NICs. The update from 1.0.0 to 1.0.1 was never working. The update from 1.0.1 to 1.0.1-rc1 was working fine. Shorty after that I tried to update it to 1.0.1-rc2 and ran into a certificate error: Internal error occurred: failed calling webhook "virtualmachines-mutator.kubevirt.io": Post "https://virt-api.harvester-system.svc:443/virtualmachines-mutate?timeout=10s": x509: certificate has expired or is not yet valid: current time 2022-05-12T212717Z is after 2022-05-12T202027Z Anybody seen this? Such a thing should never happen.... I guess.

Is there a way to make public IPs available to VMs that are assigned to the management NIC? Switches available are not managed by us and are not VLAN aware.

I'm confused by what I am seeing in VM networking. When I create a new VM, DHCP is assigning the same IP to every new VM. First point of confusion is that there isn't a DHCP server available outside the cluster and I haven't installed one inside yet. So where is this DHCP address coming from? It's also a specific /24 cidr that I often use in lab networks, so I am curious if I set that subnet somewhere during install. Note that I am using one NIC with a public IP. Is this expected behavior?

Need some help. I'm trying to boot the RancherOS.ISO and the VeeamRecovery.ISO but I keep getting the UEFI Interactive Shell Environment. I'm going to startup a RancherVM and attempt to migrate a VM by restoring a backup using Veeam.

Is it going to break my system if I run Rancher in a VM inside harvester and then use that Rancher instance to manage harvester?

Any way to change the VIP address?

Wonder how hard it would be to add https://www.dell.com/support/home/en-us/drivers/driversdetails?driverid=rx6p0&oscode=sle15&productcode=poweredge-r740 into Harvester

How do you assign VIP to a different NIC than mgmt in an ISO install?

So what's the status on the harvester CSI driver for k3s?