-
Notifications
You must be signed in to change notification settings - Fork 716
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
shareProcessNamespace not working with TFJob #902
Comments
I think we need to reproduce it first. We use the template directly to create the pod: https://github.com/kubeflow/tf-operator/blob/master/pkg/controller.v1beta1/tensorflow/pod.go#L178. It should work well with all fields in the template. |
@dpaks Can you provide the full pod spec for the actual pods created by TFJob e.g
As @gaocegege says tf-operator should be passing the fields through directly to the pod template spec. If its not then its a bug in tf-operator but if it is then something outside tf-operator is going on. |
I am closing the issue since it is stale. But feel free to leave comments if you still have problems. |
I have the same issue when using tf-operator v0.3.0. |
Issue-Label Bot is automatically applying the labels:
Please mark this comment with 👍 or 👎 to give our bot feedback! |
Using kubeflow v0.3.4 and kube 1.12
shareProcessNamespace works when used with Pod spec.
shareProcessNamespace doesn't work when used with TFJob spec.
I tried both on the same Ubuntu 18.04 v4.15 machine.
The text was updated successfully, but these errors were encountered: