Zespre Chang

Test Plan ========= Steps ----- 1. Install Harvester with updated harvester-installer 1. After the installation is completed, check the dashboard console, its layout should look like the following:

Hi @bashofmann, we have spotted the root cause. This is particularly triggered by the http proxy settings. The readiness probe tries to hit the endpoint with HTTP GET request, and...

Today, I did another round of Harvester upgrade on a 4-node cluster and tried my best to collect all the rancher pods' logs with a simple script while upgrading: [rancher-pod-logs.tar.gz](https://github.com/rancher/rancher/files/9827075/rancher-pod-logs.tar.gz)...

My envision for this requirement is to utilize VLAN and VxLAN as providers for the Harvester VM Network. VM Network should be an abstration to the implementation details of the...

Hi @mauriiciodias! Yes, it could be one of the reasons. With the same amount of data to transfer, there will be more packets to transmit, given a lower MTU value,...

@mauriiciodias, I'm curious about the topology of your network on which you conducted the bandwidth test. Could you share if those two devices that run the `iperf` command are directly...

## Test Plan *Upgrade* 1. Prepare a Harvester cluster of version 1.2.1 2. Start the upgrade with v1.2-head ISO iamge 3. After the upgrade ended successfully, log in to each...

## Test Plan 1. Install Harvester v1.2.1 2. Upgrade to v1.2-head 3. Intentionally break the upgrade when the Harvester version becomes the new version (by removing the Upgrade CR) 4....

Though the feature is not well-integrated into Harvester, there are manual ways to restrict the number of IP addresses being requested. It depends on where you want to enforce such...

I also found that it's impossible to upgrade a single-node cluster from `master-head`. The request get rejected by the webhook because the `mcc-harvester` bundle is not in a good state,...