Closed yuanchen8911 closed 2 months ago
/cc @Huang-Wei
/ok-to-test
@yuanchen8911 could you update the readme
Updated README.md
.
@jklaw90, may I have it reviewed? Thanks!
/lgtm
Thanks for your pr @yuanchen8911
/lgtm
Thanks for your pr @yuanchen8911
Would you approve it as well? Thanks!
@ingvagabund, thanks for reviewing the PR. I've made the suggested changes to address your comments. Can you take another look please?
/lgtm
I believe this would be the first time that we're adding a field to v1alpha2 (but not v1alpha1). I think that's ok, given that it's being deprecated and removed in 1.31.
Just wanted to note that.
/approve as I believe all of @ingvagabund comments were addressed
/lgtm as I believe @jklaw90 already did
Thank you for your contribution @yuanchen8911 and being patient with us
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: a7i
The full list of commands accepted by this bot can be found here.
The pull request process is described here
This will be included as part of v0.30
soon 🤞🏼 ™️
/lgtm
/approve as I believe all of @ingvagabund comments were addressed
/lgtm as I believe @jklaw90 already did
Thank you for your contribution @yuanchen8911 and being patient with us
Thank you all for reviewing the PR!
The current
RemoveFailedPods
strategy includes a parameterreason
from a terminated container's status (state). In addition toreason
, the fieldexitCode
in a container's status, which describes the exit status from the last termination of a container, can provide additional and useful information about a container's termination.A common use case is AI/ML training jobs often inject/run pre-flight health checks in initContainers and take actions according to the
exitCode
value when an initContainer fails, e.g., deleting the scheduled job pod viaDescheduler
.This PR adds a terminated container's
exitCode
as an additional parameter to theRemoveFailedPods
strategy.Fix https://github.com/kubernetes-sigs/descheduler/issues/1380