Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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] Support Kubeflow MPIJob in MultiKueue #2880
[Feature] Support Kubeflow MPIJob in MultiKueue #2880
Changes from all commits
1962437
422ae06
e10f9f7
edeeb9c
2ae47f5
f4b2402
acb28e2
f8d28b4
fdcbc95
3322390
69d10c7
cba68de
467b4ee
963e44a
8daa5f7
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why is it only a problem for integration and not E2E?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let me explain.
Integration tests suit requires to specify the CRD directory and it doesn't care about the customise.yaml there, only plain CRDs -
kueue/test/integration/multikueue/suite_test.go
Line 94 in afb4946
Thus we can't have MPIJob CRD from training-operator there, we need to physically remove the file from the folder.
E2E doesn't care about the MPIJob file, because we have our own kustomize in test/e2e/config/multikueue, where we patch it so MPIJob CRD is deleted.
As you can see we have different needs depending on the test, that can't be satisfied with the current approach.
Previously I had combined the two by using sed to remove MPIJob file entry from original kustomize and also delete the fie from the folder.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the details!
It makes me think that we need a note on this page https://kueue.sigs.k8s.io/docs/tasks/run/kubeflow/mpijobs/ explaining that you need to disable the MPI from training-operator if using both.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are you reverting these changes after testing?
Like here:
kueue/hack/multikueue-e2e-test.sh
Line 109 in 467b4ee
kueue/hack/e2e-common.sh
Lines 97 to 99 in 467b4ee
If not, users may accidentally commit unnecessary changes to this file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't, good point I will add the restore
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
isn't this file outside of the tracked files?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No. It's on the git and yq will edit this file.