From f2be66825583bc338e0bbc9bc8b793eae48341f6 Mon Sep 17 00:00:00 2001 From: Scott Leggett Date: Thu, 18 Apr 2024 22:28:11 +0800 Subject: [PATCH] chore(docs): add note about cronjobs being interrupted --- docs/concepts-basics/lagoon-yml.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/concepts-basics/lagoon-yml.md b/docs/concepts-basics/lagoon-yml.md index 21add8f274..9dbba693c1 100644 --- a/docs/concepts-basics/lagoon-yml.md +++ b/docs/concepts-basics/lagoon-yml.md @@ -469,6 +469,10 @@ cronjobs: you need a complex or multiline cron command, you must put it in a script that can be used as the command. Consider whether a [pre- or post-rollout task](#tasks) would work. +!!! danger + Cronjobs run in Kubernetes pods, which means they can be interrupted due to pod rescheduling. + Therefore when creating a cronjob you must ensure that the command can be safely interrupted and re-run at the next cron interval. + * `service`: Which service of your project to run the command in. For most projects, this should be the `cli` service.