I think the parent poster was referring to the fact that Cron jobs can act purely on local state, and that's OK. For example, if I had a traditionally deployed

I think the parent poster was referring to the fact that Cron jobs can act purely on local state, and that's OK. For example, if I had a traditionally deployed (i.e. not in K8S / a PaaS / similar) backend app that accepted file uploads, then passed those off to something else, I'd be streaming the uploads to a temporary holding directory on disk. I'd then have a CronJob that clears stale items from the temp dir. If the server fails, that's OK that the CronJob didn't run. There are still plenty of use cases for traditional cron.