Skip to content

Add support for pods to differentiate between a scale down and a shutdown events #5248

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

Open
mattrpav opened this issue Apr 16, 2025 · 2 comments
Labels
sig/apps Categorizes an issue or PR as relevant to SIG Apps.

Comments

@mattrpav
Copy link

mattrpav commented Apr 16, 2025

Enhancement Description

  • Support an optional lifecycle hook for signaling scale down
    or
  • Support a flag or argument to existing PreStop lifecycle hook to indicate scale down

Background

Currently, there is not a way for a workload running in pod to differentiate between a scale down and a shutdown. Pod shutdown down scenarios are common for upgrades, Kuberentes patching, or moving the pod to a different node for Node patching.

Maintenance windows would be lower for stateful workloads if they were able to differentiate between scale down and shutdown in order to only handle draining or transferring of data during scale down, instead of having to drain for every shutdown scenario.

/sig apps

@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Apr 16, 2025
@mattrpav
Copy link
Author

/sig apps

@k8s-ci-robot k8s-ci-robot added sig/apps Categorizes an issue or PR as relevant to SIG Apps. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Apr 16, 2025
@github-project-automation github-project-automation bot moved this to Needs Triage in SIG Apps Apr 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sig/apps Categorizes an issue or PR as relevant to SIG Apps.
Projects
Status: Needs Triage
Development

No branches or pull requests

2 participants