Skip to content

docs: Add warning about job TTL and delete policies #561

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.

Sign up for GitHub

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

Merged
michaeljguarino merged 3 commits into from
Jan 16, 2026
Merged

docs: Add warning about job TTL and delete policies #561

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
8aaeaa9
add warning about hook Job TTL and delete policies
maciaszczykm Jan 16, 2026
020e93c
clarify hook resource deletion behavior and update warning about mani…
maciaszczykm Jan 16, 2026
cb6576c
clarify that only jobs and pods can be automatically deleted by hooks
maciaszczykm Jan 16, 2026
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
13 changes: 9 additions & 4 deletions pages/plural-features/continuous-deployment/resource-application-logic.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -111,12 +111,17 @@ annotation. Multiple policies can be comma-separated.
Use `hook-succeeded` and/or `hook-failed` to delete the resource after it completes successfully or fails, respectively.
If no delete policy is set, the resource will be kept.

{% callout severity="info" %}
Only jobs and pods are automatically deleted. Other resources will need to be deleted manually or via other automation.
{% /callout %}
Only jobs and pods can be automatically deleted. Other resources need to be deleted manually or via other automation.

{% callout severity="warning" %}
When a manifest of a hook is updated, the operator will reapply the resource even if it has already completed.

{% callout severity="warning" %}
If a job manifest sets `ttlSecondsAfterFinished`, Kubernetes will delete it after it completes.
The agent will then see the resource as missing and recreate it unless the manifest also
includes a hook delete policy via `deployment.plural.sh/sync-hook-delete-policy` or `helm.sh/hook-delete-policy`.

To avoid a delete/recreate loop, ensure the delete policy contains a value we accept: `hook-succeeded` and/or
`hook-failed`. With a valid delete policy set, completed hooks won’t be recreated unless their manifest changes.
{% /callout %}

### Example
Expand Down
Loading