docs: clarify Kubernetes pod cleanup policy scope [EDU-1441] - #1846
Merged
justinegeffen merged 3 commits intoSep 14, 2026
Merged
Conversation
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
✅ Deploy Preview for seqera-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
justinegeffen
added
1. Editor review
christopher-hakkaart
approved these changes
Sep 13, 2026
christopher-hakkaart
left a comment
christopher-hakkaart
left a comment
Member
There was a problem hiding this comment.
Style guide applied and approved.
justinegeffen
deleted the
docs/EDU-1441-k8s-pod-cleanup-policy-scope
branch
September 14, 2026 17:07
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
1. The Pod cleanup policy bullet — 9 pages. Now states that the policy governs the head pod, defines On success / Always / Never, and links to the new troubleshooting entry for task pods.
2. New troubleshooting entry, "Kubernetes pods remain after a run ends" — 3 pages. Explains the three-way split, warns about the autoscaler and cost consequence, and gives
kubectlremediation.https://github.com/seqeralabs/docs-internal/pull/89