sourcegraph / sourcegraph/deploy-sourcegraph-helm
Background services livenessProbe is too aggressive
Nobody has claimed this yet.
- Dominant language
- Go Template
- Stars
- 18
- Forks
- 24
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 13
Description
The background services running for sourcegraph should not require that high request/limits, we are running repo-updater with 50m cpu and 128Mi memory for instance, this makes the container fail to start before the livenessProbe(which will restart it after 3 seconds as current configured) and put the pod into a crash loop.
Setting a intialDelaySeconds to 5s, or startupProbe, or simply making the livenessProbe of the non-user hot path services less aggressive would allow these services to run with less resources.
Contributor guide
No contributing guide indexed for this repository
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
Inspect the Helm templates for the background services, especially repo-updater, and find their livenessProbe and resource settings. Compare the probe timing with the stated 50m CPU and 128Mi memory allocation; done means a rendered configuration lets low-resource services start without entering a crash loop.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100