Breaking (v2): require `livenessProbe` and `readinessProbe` to be set separately for workers
As a failed livenessProbe kills the pod, setting a livenessProbe that applies to all deployments and workers can end up having killed containers unnecessarily.
Proposal
!103 (merged) introduced idea of separate setting for workers, but falls back to .Values.livenessProbe
, .Values.readinessProbe
.
Remove this fallback in v2.