We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
kubeflow/training-operator@984adc2#diff-c3cd90fce520caf42f3e75efbc527abd0d119271103de3fe6f0168e8c5fb8c33L30
Kubeflow/common unifies the label for all jobs, while we are still using tf-replica-type in arena. Should we update to replica-type?
cc @cheyang
The text was updated successfully, but these errors were encountered:
cc @happy2048
Sorry, something went wrong.
we have using https://github.com/AliyunContainerService/tf-operator/tree/v1.0-aliyun-branch to build tf-operator for arena, this branch includes some custom features different from kubeflow/tf-operator.
Can we merge the change AliyunContainerService/tf-operator@61b5919 to the mainstream?
ok, I will commit a PR.
happy2048
No branches or pull requests
kubeflow/training-operator@984adc2#diff-c3cd90fce520caf42f3e75efbc527abd0d119271103de3fe6f0168e8c5fb8c33L30
Kubeflow/common unifies the label for all jobs, while we are still using tf-replica-type in arena. Should we update to replica-type?
cc @cheyang
The text was updated successfully, but these errors were encountered: