Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: add note about cronjobs being interrupted #3711

Merged
merged 1 commit into from
May 27, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions docs/concepts-basics/lagoon-yml.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down