Leon
Leon
> 对于 component scale out， 现在主要瓶颈是，无法判断集群发生了什么变化，以及是否处于这此变化的最终状态。 具体来说是在服务启动成功后，脚本很难知道，这此启动是因为扩容，还是因为节点被人为重启，或者是发生了故障。 > > component scale 的 action 需求： > > 1. action 的触发需要一个明确的调用，比如 script run，web hook。 > 2. action 的需要的信息如下 > > * scale...
/cherry-pick release-0.9
/approve for test
/cherry-pick release-1.0-beta
Btw, the cluster name is also lost.
> @leon-inf any updates? 😉 From the description above, I cannot figure out what problem you are encountering. Can you provide more detailed information about the scenario? For example, the...
I have tried to add a UT to simulate the scenario you described, can you help me to confirm whether this is the case? Or you can modify it directly...
BTW, it would be much more convenient if you could provide the complete CMPV, along with the cluster specs regarding service versions and/or comp-def.