This message was deleted.
# platform-blueprints
s
This message was deleted.
a
Off the top of my head, might be a bit overkill if you're not already in Kubernetes, but if you are, why not run them as Kubernetes CronJobs? You can track the run status, pause and resume the job, and in terms of history, you could simply use your observability stack to access historical logs and metrics.
l
I also want to run dependent jobs, how it can be possible via Kubernetes cron job
a
Your CronJob, when it runs, can write Job resources to the same Kubernetes to run downstream jobs. If you need to define more formal pipelines of jobs which run in a particular sequence, you can look into frameworks like Knative which allow you to do just that.