Kiefer Chang

Close since it can't be produced. Please re-open if you hit this issue again.

@Vicente-Cheng that's indeed what the field is for.

Hit the same issue when provisioning box-less VM: ``` $ cat Vagrantfile Vagrant.configure("2") do |config| config.vm.define :pxeclient do |pxeclient| pxeclient.vm.provider :libvirt do |domain| domain.boot 'network' end end end $ vagrant...

@tjjh89017 As a record, could you comment on why we don't handle pod replicas from the ManagedChart level? Instead, do it on each component (Prometheus, alert manager, grafana, ...etc). Thanks.

The feature works great. Please help make the logging message more meaningful: ``` time="2022-09-28T01:22:17Z" level=info msg="storage network change: {\"vlan\":2,\"clusterNetwork\":\"storage\",\"range\":\"172.16.5.0/24\"}" time="2022-09-28T01:22:17Z" level=info msg="Rancher Monitoring: true" time="2022-09-28T01:22:17Z" level=info msg="prometheus: 0" time="2022-09-28T01:22:17Z" level=info...

> It will have some upgrade issues if users manually configured Longhorn storage-network settings. > > * Sync problem > > * Should we sync Longhorn storage-network setting to Harvester...

@TachunLin Note the check takes effect until the next release (e.g., upgrade from v1.1.0 to another version). For v1.0.3, the best we can do so far is to fail the...

@lanfon72 The issue is merely for tracking that we should handle the alert manager's PVC when enabling/disabling the dedicated network. At this moment, all volumes can only reside on the...

@guangbochen no objection. Benchmark is needed and perhaps we need to pre-allocate some CPU resources for ksmd.

@starbops @Vicente-Cheng Just found for 1-node and 2-node cluster, `instance-manager-r` count never become `1. I need to do more investigation.