0

We're using spring batch remote partitioning based on spring-cloud-deployer-kubernetes, for some reason worker pods were not getting deleted after the worker execution. Wondering what is the configuration that kicks off the cleanup through TaskLauncher.

Thanks

Magesh P
  • 11
  • 1

1 Answers1

1

Though the PODs stick around, they won't be running once when the business-logic/operation in the app completes. The container/POD will switch to "Complete" status when they are done with the operation. In other words, they won't be consuming any resources. That is the current design - no other cleanup routine will be triggered.

We are thinking of optionally also providing a flag to clean up resources, so there's no residue of previous runs.

If you're observing something other than what was described above, feel free to update the description and clarify with more details. Perhaps also include the stream/task definition, and the pod-list output.

Sabby Anandan
  • 5,636
  • 2
  • 12
  • 21
  • Thanks, there was a tomcat listener running in worker pod too, and the was stopping to flip the status to complete. – Magesh P Apr 27 '19 at 17:02