What would you like to be added:
If we want to use the current MPIJob MultiKueue feature, we need to uninstall the mpi-operator from the management cluster.
But, since the mpi-operator v0.6.0, we started to support the managedBy feature similar to the batch/v1 Job.
Hence, we want to support it by implementing in the following:
Implement the defaulting webhoooks similar to Job and JobSet:
And other needed implementations to support it if it exists.
Why is this needed:
The MPIJob with managed feature allows us to install the mpi-operator to management and worker clusters so that we can easily introduce multi-cluster MPIJob dispatching and give the possibility of running the MPIJob in the management cluster as well.
Completion requirements:
This enhancement requires the following artifacts:
[ ] Design doc
[ ] API change
[x] Docs update
The artifacts should be linked in subsequent comments.
What would you like to be added: If we want to use the current MPIJob MultiKueue feature, we need to uninstall the mpi-operator from the management cluster. But, since the mpi-operator v0.6.0, we started to support the managedBy feature similar to the batch/v1 Job.
Hence, we want to support it by implementing in the following:
IsJobManagedByKueue
: https://github.com/kubernetes-sigs/kueue/blob/4199c9dd9ce89636eb4e72f5cebb3c9adfba3f0c/pkg/controller/jobs/mpijob/mpijob_multikueue_adapter.go#L89-L91And other needed implementations to support it if it exists.
Why is this needed: The MPIJob with managed feature allows us to install the mpi-operator to management and worker clusters so that we can easily introduce multi-cluster MPIJob dispatching and give the possibility of running the MPIJob in the management cluster as well.
Completion requirements:
This enhancement requires the following artifacts:
The artifacts should be linked in subsequent comments.