goodrain
关于 v5.11.0 版本健康检测配置为 重启 时 滚动更新无效的问题
版本 v5.11.0-release-1340c6c32-2023-02-01-06-allinone ,可能之前版本也有这个问题
健康检测改为 重启 时，更新实例时，不是滚动更新。 改为 下线 模式时，滚动更新正常。
Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿
Title: About the problem that the rolling update is invalid when the v5.11.0 version health detection is configured as restart
健康检测改为 重启 时，更新实例时，不是滚动更新 是什么意思呢？
我尝试过以下四种情况，都是没有问题的。
- 组件健康检测设置为重启，然后再启动组件，再进行更新，有滚动更新的流程。
- 组件健康检测设置为下线，然后再启动组件，再进行更新，有滚动更新的流程。
- 组件健康检查先设置为下线，启动组件，再调整为重启，再进行更新，有滚动更新的流程。
- 组件健康检查先设置为重启，启动组件，再调整为下线，再进行更新，有滚动更新的流程。
Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿
When the health check is changed to restart, when the instance is updated, it is not a rolling update What does it mean?
I have tried the following four situations, all without problems.
- The component health check is set to restart, then start the component, and then update, there is a rolling update process.
- Set the component health check to be offline, then start the component, and then update it. There is a rolling update process.
- Set the component health check to offline first, start the component, then adjust it to restart, and then update it. There is a rolling update process.
- The component health check is first set to restart, start the component, then adjust it to offline, and then update. There is a rolling update process.
复现步骤：
1、选择一个启动时间相对较长的应用（例如：平均4分钟启动完成）
2、健康检查配置信息：
（1）初始等待时间：240秒（保持与应用平均启动时长接近）
（2）检测间隔时间：3秒
（3）检测超时时间：20秒
（4）连续成功次数：1
（5）不健康处理方式：重启
3、当前运行实例：1个运行中
4、点击“更新（滚动）”：可以发现1秒钟完成了组件升级，但是应用实际上还处于启动中，无法正常提供服务
Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿
In this part, we temporarily consider adding the configuration of K8s properties. The priority configured in K8s properties is higher than the priority of interface configuration. Planned to optimize in version 5.15.3 or 5.16
Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿
This problem has been solved in version 5.17 by supporting advanced properties, so I will close this issue and you can open it at any time if the problem still exists.