Closed Mr0grog closed 1 year ago
Instead of running the import job as a cron script on a random EC2 VM, run it as an actual CronJob in Kubernetes with everything else. This also cleans up the docs around jobs.
Why do this now? See:
Work not visible here:
Instead of running the import job as a cron script on a random EC2 VM, run it as an actual CronJob in Kubernetes with everything else. This also cleans up the docs around jobs.
Why do this now? See:
Work not visible here: