[k8s] Add configurable master pod timeout to Kubernetes backend #1390
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request introduces a new configurable parameter,
master_timeout
, to the Kubernetes backend.Motivation
There may be jobs that last more than 10 minutes, which is the default master pod duration. Although the master pod is expected to restart automatically, there are cases where it does not restart or after restarting some jobs are lost, resulting in jobs shown in Lithops logs as Pending.
The new
master_timeout
parameter mitigates these issues by allowing to configure a suitable timeout based on the job requirements.Developer's Certificate of Origin 1.1