Automatic restarts for Containers and Executables
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 189
- Forks
- 24
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 18
Description
### Motivation
There are cases when a Container or Executable used as a dependency service is not as resilient to transient errors as one would like it to be. In those cases an automatic restart upon failure is a big boost to developer productivity.
### Initial design thoughts
If we do this, we should be very careful about avoiding thrashing, i.e. restarting in a tight loop. K8s does it well with "exponential backoff" for repeatedly failing restarts.
For containers we might be able to leverage what the container orchestrator supports, but the support may vary from orchestrator to orchestrator, so DCP might need to backfill in some cases and we might model the restart support as optional in our container orchestrator abstraction layer.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are identified in the issue. Start by reviewing the Container and Executable dependency-service abstractions and the container orchestrator layer, then define restart and backoff behavior; done would require an agreed design and implementation scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100