Sirius Devops
abecefe0e1
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. |
||
|---|---|---|
| .. | ||
| configmaps | ||
| dashboard | ||
| data-service | ||
| execute-service | ||
| network-policies | ||
| news-service | ||
| routes | ||
| secrets | ||
| kustomization.yaml | ||