Simplify the deployment to kubernetes
For now, there is no way to know if a job that has been started is still alive or if it has crashed silently (if the pod had an OOM error, for example).

When deploying a new version, it's annoying because we have to first stop all the workers (replicas=0), then cancel the jobs (STARTED => WAITING), then deploy.

Instead of this, we could create a new kubernetes "Job" (as the one that migrates MongoDB) that would cancel all the jobs in "STARTED" status, before launching the workers again.

thanks @XciD for the idea.
Simplify the deployment to kubernetes: For now, there is no way to know if a job that has been started is still alive or if it has crashed silently (if the pod had an OOM error, for example).

When deploying a new version, it's annoying because we have to first stop all the workers (replicas=0), then cancel the jobs (STARTED => WAITING), then deploy.

Instead of this, we could create a new kubernetes "Job" (as the one that migrates MongoDB) that would cancel all the jobs in "STARTED" status, before launching the workers again.

thanks @XciD for the idea.