Maurice a869269591 fix(deploy): follow PORT in every probe, wait for a slow boot, and probe the database ...

Changing PORT left the Dockerfile and compose healthchecks, the chart's
containerPort, Service target and probes on 3000, so the container went
unhealthy and Kubernetes restarted it in a loop. All of them follow PORT
now. The chart gains a startup probe (ten minutes for a first boot, a
long migration or a restore at boot, which liveness used to kill after
about 105 s), a readiness probe on the new /api/health/ready that asks
the database, extraEnv and extraEnvFrom for the settings the chart does
not list, slots for the four secrets it had none for, and the
DEFAULT_LANGUAGE and MCP_MAX_SESSION_PER_USER values it documented but
never set. The Dockerfile no longer hides a failed npm ci behind a ';',
pins gosu, and the language lists name all 27 locales.

2026-10-07 16:40:40 +02:00

..

templates

fix(deploy): follow PORT in every probe, wait for a slow boot, and probe the database

2026-10-07 16:40:40 +02:00

Chart.yaml

chore: bump version to 4.3.3 [skip ci]

2026-09-26 12:23:05 +00:00

values.yaml

fix(deploy): follow PORT in every probe, wait for a slow boot, and probe the database

2026-10-07 16:40:40 +02:00