fix(execute-service): update startupProbe to /health/ready with 30 failureThreshold

The service was 'running but not ready' because:
- startupProbe used /health (always-ok) with only failureThreshold: 6 (~30s grace)
- Executor initialization (Hyperliquid SDK network calls + Solana client) takes longer

Now uses /health/ready (checks actual executor state) with failureThreshold: 30 (~5min grace), matching the pattern used for data-service and dashboard.

Also updated Helm template for consistency.
This commit is contained in:
Sirius Devops 2026-05-25 06:09:20 +00:00
parent ceb832b169
commit abecefe0e1

View file

@ -65,11 +65,11 @@ spec:
key: JWT_SECRET_KEY key: JWT_SECRET_KEY
startupProbe: startupProbe:
httpGet: httpGet:
path: /health path: /health/ready
port: 8002 port: 8002
initialDelaySeconds: 15 initialDelaySeconds: 15
periodSeconds: 5 periodSeconds: 10
failureThreshold: 6 failureThreshold: 30
livenessProbe: livenessProbe:
httpGet: httpGet:
path: /health path: /health