Spring Batch Job pods are still running after completion of job in Kubernetes Cluster

Viewed 11

Pods in the Kubernetes cluster are still running after the job is done. My assumption is that there might be a chance that Kubernetes re-schedule the pods to the other nodes and job was done on those nodes that is why it is showing Job done but how Spring will monitor re-schedule pods that is why it will again re-deploy the pods for the completion of the job.

So my question is, Do spring monitor the pods after re-scheduling the pods to other nodes

Or

If my assumption is pointless can you please suggest a possible solution?

0 Answers
Related