Background services livenessProbe is too aggressive

[BadLiveware]

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.