You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
> 💡 **NOTE:**There are other ways to delay termination, including the [`preStop` Hook](https://kubernetes.io/docs/concepts/containers/container-lifecycle-hooks/#container-hooks)
Unfortunately, containers will still receive SIGKILL after terminationGracePeriodSeconds have elapsed, regardless of the preStop hook, which is just used to delay the initial SIGTERM sent for graceful termination.
With the current wording of this note, I thought for a moment that the preStop hook would take precedence over terminationGracePeriodSeconds and preventing Kubernetes from sending SIGKILL until the hook finished running.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.
stalebot
added
the
stale
All issues that are marked as stale due to inactivity
label
Oct 12, 2024
Since #265, the documentation provides a note stating that the
preStop
hook can be used to delay termination:keda-docs/content/docs/1.5/concepts/scaling-deployments.md
Line 107 in 5ef378e
Unfortunately, containers will still receive
SIGKILL
afterterminationGracePeriodSeconds
have elapsed, regardless of thepreStop
hook, which is just used to delay the initialSIGTERM
sent for graceful termination.With the current wording of this note, I thought for a moment that the
preStop
hook would take precedence overterminationGracePeriodSeconds
and preventing Kubernetes from sendingSIGKILL
until the hook finished running.The text was updated successfully, but these errors were encountered: