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
TfJob controllers are not namespace scoped so tests aren't isolated #134
Labels
Comments
I suspect this might be causing TFJob test flakes where we see simple job test occasionally timing out waiting for a TFJob to finish. See for example #602 |
@ankushagarwal This is fixed by #894 correct? |
Yes. |
yanniszark
pushed a commit
to arrikto/kubeflow
that referenced
this issue
Nov 1, 2019
* remove the hard-coded selector * run make generate and make test
yanniszark
pushed a commit
to arrikto/kubeflow
that referenced
this issue
Nov 1, 2019
…r" (kubeflow#150) * Revert "Remove admission-webhook/bootstrap hard-coded selector (kubeflow#134)" This reverts commit fea53c8. * Update stateful-set.yaml * Update bootstrap-base_test.go * Fix build * Revert "Remove admission-webhook/bootstrap hard-coded selector (kubeflow#134)" This reverts commit fea53c8. Update stateful-set.yaml Update bootstrap-base_test.go Fix build
elenzio9
pushed a commit
to arrikto/kubeflow
that referenced
this issue
Oct 31, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Controller claims jobs in all namespaces, but our tests are trying to reuse clusters by deploying in different namespaces.
So our tests aren't isolated.
Possible fixes
The text was updated successfully, but these errors were encountered: