Repository navigation
Per-deployment restart block and jobs on the restart policy - #245
Merged
Merged
Conversation
…bs that cannot start
…f past the budget, and promote driven deployments once an instance is seen running
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Third step of the restart policy design (documentation/design/restart-policy.md).
restartblock overriding[server.restart]key by key (base,cap,stable_after,on_exhaustion,max_attempts, andbackoff_limitfor jobs). It is validated at apply time against the server policy; unknown keys and keys meaningless for the deployment's kind are rejected, by the CLI and the API.backoff_limit(default 0) allows more runs; a job that cannot start is retried on the backoff curve without limit and does not count againstbackoff_limit. A finished job keeps its instance and logs.applyonly tears deleted deployments down.