-
Notifications
You must be signed in to change notification settings - Fork 883
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
如何使得volcanojob的状态和pod的ready状态保持一致 #3455
Comments
The running state of volcano job derived from pod, so volcano job shows running state when pod is running, even pod is not ready, it's in running state, so volcano job is in running state, and volcano job is not aware of ready state of pod. |
We want to generate a ingress path to user when the pod is really ready,in volcano vcjob can not get the pod ready status ,we have to checl the pod status in application layer; it is not convenient. so if it is possble to add another status ?
…---- 回复的原邮件 ----
| 发件人 | Marty ***@***.***> |
| 发送日期 | 2024年05月10日 17:59 |
| 收件人 | volcano-sh/volcano ***@***.***> |
| 抄送人 | BurningRock ***@***.***>,
Comment ***@***.***> |
| 主题 | Re: [volcano-sh/volcano] 如何使得volcanojob的状态和pod的ready状态保持一致 (Issue #3455) |
我在用到了k8s的readyprobe探针,当业务未完成部署时 pod的ready状态未0/1。当pod的ready状态发生变化时,volcano的job的状态一直都处于running状态。检测不到volcanojob的status状态变化,这是否是volcano需要优化的地方?如果不是,怎么配置可以让volcano或者k8s感知到pod的就绪状态的变化。
Also meet the problem; pod ready status volcano cannot get ; handle it in application layer
Yeah, voclano won't care pod's ready status: )
Is there any plan to add anather status for vcjob for ready ;as we care the ready status ; in k8s,svc also check the pod ready status
Can you describe your use case here?ready status depend on container status of pod, vcjob manage pods belong to it, not container granularity.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
我在用到了k8s的readyprobe探针,当业务未完成部署时 pod的ready状态未0/1。当pod的ready状态发生变化时,volcano的job的状态一直都处于running状态。检测不到volcanojob的status状态变化,这是否是volcano需要优化的地方?如果不是,怎么配置可以让volcano或者k8s感知到pod的就绪状态的变化。
The text was updated successfully, but these errors were encountered: