-
Notifications
You must be signed in to change notification settings - Fork 706
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
MPIJob requires service names for the pods. #2090
Comments
If you want to install the training-operator and mpi-operator into the same cluster, we need to disable the MPIJob in the training-operator like this: #1972 (comment) Also, I would recommend using the MPIJob v2 (mpi-operator) since we are preparing the deprecation and removal of the MPIJob v1. #1906 |
/kind support |
@tenzen-y: The label(s) In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
If you have any other issues, feel free to open new one. |
@tenzen-y: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
The implementation in the mpi-operator repository at mpi-operator link conflicts with the one in the training-operator repository at training-operator link. BTW, considering that both repositories are actively being developed, which one should I follow for using MPIJob?
The text was updated successfully, but these errors were encountered: