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
{{ message }}
This repository has been archived by the owner on Sep 12, 2023. It is now read-only.
In the current implementation, the runPolicy.BackoffLimit is only applicable on OnFailure and Always restart policies. I was wondering if there's a reason it's not supported on the ExitCode restart policy. Often in the case of OOM, the job exits with an exit code of 137 which is rightfully a retriable error. However, it will keep restarting indefinitely since the policy is not covered by the BackOffLimit. The behavior could be to honor the backOffLimit if present, else it keeps retrying indefinitely?
I am happy to submit a PR if you think this is a reasonable change.
The text was updated successfully, but these errors were encountered:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
In the current implementation, the
runPolicy.BackoffLimit
is only applicable onOnFailure
andAlways
restart policies. I was wondering if there's a reason it's not supported on theExitCode
restart policy. Often in the case of OOM, the job exits with an exit code of 137 which is rightfully a retriable error. However, it will keep restarting indefinitely since the policy is not covered by theBackOffLimit
. The behavior could be to honor the backOffLimit if present, else it keeps retrying indefinitely?I am happy to submit a PR if you think this is a reasonable change.
The text was updated successfully, but these errors were encountered: