-
Notifications
You must be signed in to change notification settings - Fork 445
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
ignore Retain field #565
Comments
I have a question may not be related to the issue. How to support the case that the users want to create new trials for the completed experiment? Do we plan to support it? Ref #346 |
We can add support for |
/assign |
Other k8s objects follow the same convention right? eg: K8s Job |
/close since #572 merged |
/close |
@hougangliu: 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. |
in experiment.spec.trialTemplate and experiment.spec.metricsCollectorSpec,
Retain
filed is defined, which is used to delete worker job and metricCollecoter job when trial completed, but now we ignore the field when create new trial( Trial struct has no counterpart field of the two kind ofRetain
)should we drop
Retain
in experiment and always delete worker job and metricCollecoter job when trial completed? or add two new field in trial.spec?/cc @richardsliu @gaocegege @johnugeorge @YujiOshima which one do you prefer?
The text was updated successfully, but these errors were encountered: