It would be worth making this clearer by calling out that a Cronjob can run inside of the pod defined in the service, and if the interval of the cron schedule is 30 minutes or less, it will run inside of the service pod, but if the schedule is more than 30 minutes, it will be turned into a native kubernetes cronjob and run separately to the service but using the same image that the service uses.
As for timezones, cronjobs running in-pod will be impacted by the pods timezone (if it is set, otherwise UTC), where native jobs will be UTC (or whichever timezone the cluster is configured to run on)
Currently the documentation for cronjobs doesn't clearly define the difference between in-pod cronjobs, and native cronjobs https://docs.lagoon.sh/using-lagoon-the-basics/lagoon-yml/#cron-job-example
It would be worth making this clearer by calling out that a Cronjob can run inside of the pod defined in the
service, and if the interval of the cron schedule is 30 minutes or less, it will run inside of theservicepod, but if the schedule is more than 30 minutes, it will be turned into a native kubernetes cronjob and run separately to theservicebut using the same image that theserviceuses.As for timezones, cronjobs running in-pod will be impacted by the pods timezone (if it is set, otherwise UTC), where native jobs will be UTC (or whichever timezone the cluster is configured to run on)