Skip to content

Make executor clean up pods stuck terminating more quickly#4697

Merged
JamesMurkin merged 2 commits intomasterfrom
more_responsive_pod_cleanup
Feb 17, 2026
Merged

Make executor clean up pods stuck terminating more quickly#4697
JamesMurkin merged 2 commits intomasterfrom
more_responsive_pod_cleanup

Conversation

@JamesMurkin
Copy link
Contributor

This config is used to determine when the executor needs to step in to force kill a pod

  • The timeout is in addition to the pods termination grace period second
  • The timeout is purely give k8s some time to act

Waiting 30s for k8s to take action before calling force kill ourselves should be OK (we're only speeding up what k8s should be doing already)

This should make cleaning up pods stuck in terminating states that k8s can't handle far more responsive

This config is used to determine when the executor needs to step in to force kill a pod
 - The timeout is in addition to the pods termination grace period second
 - The timeout is purely give k8s some time to act

Waiting 30s for k8s to take action before calling force kill ourselves should be OK (we're only speeding up what k8s should be doing already)

This should make cleaning up pods stuck in terminating states that k8s can't handle far more responsive

Signed-off-by: JamesMurkin <jamesmurkin@hotmail.com>
@JamesMurkin JamesMurkin changed the title Make executor clean up stuck terminating pods more quickly Make executor clean up pods stuck terminating more quickly Feb 17, 2026
@JamesMurkin JamesMurkin marked this pull request as ready for review February 17, 2026 12:20
@JamesMurkin JamesMurkin enabled auto-merge (squash) February 17, 2026 13:19
@JamesMurkin JamesMurkin merged commit 7929e74 into master Feb 17, 2026
15 checks passed
@JamesMurkin JamesMurkin deleted the more_responsive_pod_cleanup branch February 17, 2026 13:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants