摸鱼喵
@zijin520 The default scheduling policy of k8s is biased towards load balancing, you can check the load of the next two nodes, perhaps k8s thinks that the other node has...
@zijin520 - For the device and deviceprofile issues, this is due to the yurt-iot-dock version issue, currently our api support for edgex v3 is not stable, the latest version has...
The root cause of this is that yurtappset might launch multiple identical components (like two consuls or two core-data) in the same nodepool, and then eventually only one is guaranteed...
This issue had been completely solved in #2029.
/assign @wangxye
The complete logic needs to wait until the k8s api of kruise is upgraded.
For the case of vscale failure, my current idea is to start the rollback mechanism, is it necessary to provide users with some configurable interfaces? Because for vscale, rolling back...
Do I need to add more details to `expectationDiffs`? For example, which container needs vertical scaling. But this can make the structure too bloated.