Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[feature request] 原地升级进入到 PreparingUpdate 阶段时,能否也提供 apps.kruise.io/inplace-update-state 信息,以告知哪个容器正在进行原地更新? #1906

Open
NickPak opened this issue Feb 7, 2025 · 3 comments
Assignees

Comments

@NickPak
Copy link

NickPak commented Feb 7, 2025

What would you like to be added:
我的业务中有这样一个需求,Pod中有多个容器,每个容器进行原地更新时的处理会稍有不同,比如 A 容器在进入原地更新时,不用等待 Lifecycle Hook 机制,而 B 容器在进入原地更新时需要等待 Lifecycle Hook 机制,但我尝试后发现,当容器进入 PreparingUpdate 阶段时,没有任何信息能拿到哪个容器正在进行原地更新,也没有 apps.kruise.io/inplace-update-state 注解。

可否在更新的任意阶段都增加 apps.kruise.io/inplace-update-state 信息?

或者,是否还有其他方案能在 PreparingUpdate 阶段获取到哪个容器正在执行原地更新?

Why is this needed:

@chrisliu1995
Copy link
Member

chrisliu1995 commented Feb 11, 2025

请问之前是有在openkruise/kruise-game#161 这个issue下回复吗?

@NickPak
Copy link
Author

NickPak commented Feb 14, 2025

请问之前是有在openkruise/kruise-game#161 这个issue下回复吗?
是的,后来通过爬文档解决了所提的问题,非常感谢

@chrisliu1995
Copy link
Member

请问之前是有在openkruise/kruise-game#161 这个issue下回复吗?
是的,后来通过爬文档解决了所提的问题,非常感谢

是通过服务质量+生命周期钩子解决的吗?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants