Guangbo

close this epic issue since all feature-related items are merged or verified, the doc and HEP will be tracked by independent issues accordingly.

Yes, adding a proper messages when unset the registration url would be useful, so users will also know they need to delete the cluster from the upstream Rancher. cc @WuJun2016,...

Yes, I think we can start with benchmarking the [KSM config](https://www.linux-kvm.org/page/KSM) first and add related monitoring metrics to it. This issue can be tracked via the epic issue https://github.com/harvester/harvester/issues/1899, any...

this issue seems duplicate with https://github.com/harvester/harvester/issues/2175? cc @FrankYang0529

Got it thanks, then we will need a setting to allow users to config a private registry and upload a custom CA cert of the Harvester cluster.

@Vicente-Cheng @bk201 we may need to consider to patch the original `longhorn` SC to none-default SC druing v1.1 upgrade, after adding the storage tiering support we will have a new...

@Vicente-Cheng waiting for the storage tiering UI changes, there will a new storage class page and users will be allowed to select SC during VM/volume/image creation. https://github.com/harvester/dashboard/pull/415

thanks for the info and we will consider bringing back the multi-arch support when it is available on the `kubevir` side.

For the v1.1.0 release, we may consider providing the manual workaround solution here if users encounter it, further investigation and solution can be done via the v1.1.1 release, thanks.

@yaocw2020 network-controller is disabled by default in the integration test https://github.com/harvester/harvester/blob/master/tests/integration/runtime/construct.go#L50, I can't recall exactly why, but maybe due to the limitation of kind cluster.