Since we've moved maintain-harbor to kubernetes cronjobs directly and no longer use toolforge-jobs to deploy maintain-harbor jobs, we need to persist the logs generated every time the cronjobs run. This also applies to any other current or future k8s component that we feel we need to persist the log.
Best solution will be to feed everything into logstash or something but since toolforge doesn't yet have a centralized logging solution, a good middle ground will be to write the logs to the worker's journald or a /var/logs file. Persisting the log on the worker comes with the problem of the logs being scattered across the different workers (since the cronjob pods will potentially run on different workers every time they are created), but it's better than losing the logs completely.