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

Do not handle job update #74

Merged
merged 1 commit into from
Apr 9, 2019
Merged

Do not handle job update #74

merged 1 commit into from
Apr 9, 2019

Conversation

hzxuzhonghu
Copy link
Collaborator

fixes: #68

@TommyLike
Copy link
Contributor

Instead of blocking it, I am wondering whether we can support this by a pod replacement totally?

@hzxuzhonghu
Copy link
Collaborator Author

It maybe not that simple, I can think of a case: some pods have finished successfully.

@TommyLike
Copy link
Contributor

hmm, @hzxuzhonghu by which means we need ignore considering those successful pods while need update the spec?

@hzxuzhonghu
Copy link
Collaborator Author

This is by accident or attack

@k82cn k82cn merged commit 6ab31a1 into master Apr 9, 2019
@k82cn k82cn deleted the update-job branch April 9, 2019 03:41
kevin-wangzefeng pushed a commit to kevin-wangzefeng/volcano that referenced this pull request Apr 30, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

How do we support Job.Spec update
3 participants