You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Finalizer prevents accidentally removing the TrainingRuntime when the referenced TrainJob has already been created.
If we do not have such a mechanism, the TrainingRuntime will be accidentally removed, and TrainJob will be disrupted since the actual Jobs (JobSet) will be built by TrainingRuntime and TrainJob.
Love this feature?
Give it a 👍 We prioritize the features with most 👍
The text was updated successfully, but these errors were encountered:
What you would like to be added?
We would like to implement the Finalizer
trainer.kubeflow.org/resource-in-use
mechanism against TrainingRuntime and ClusterTrainingRuntime.Why is this needed?
The Finalizer prevents accidentally removing the TrainingRuntime when the referenced TrainJob has already been created.
If we do not have such a mechanism, the TrainingRuntime will be accidentally removed, and TrainJob will be disrupted since the actual Jobs (JobSet) will be built by TrainingRuntime and TrainJob.
Love this feature?
Give it a 👍 We prioritize the features with most 👍
The text was updated successfully, but these errors were encountered: