immich: fix stale NFS bind-mount causing 500 on upload

After a CARP failover or f-host reboot the node host remounts NFS
cleanly but already-running pods keep their old stale bind-mount,
causing writes to return ESTALE (errno 116). Three changes to auto-heal:

1. immich-valkey: replace ping-only liveness with a write-probe
   (valkey-cli ping + echo to /data/.nfs-write-probe), so a stale
   /data mount fails the probe and kubelet restarts the container with
   a fresh bind-mount.

2. immich-server: add label nfs.stale-restart/enabled=true so the
   node-level nfs-mount-monitor can exec a write-probe into the pod
   and force-delete it if writes fail. Cannot do this via Helm values —
   the upstream chart hardcodes an httpGet liveness and its Sprig merge
   refills httpGet even when set to null, producing an invalid
   dual-handler probe rejected by the k8s API.

3. nfs-mount-monitor/check-nfs-mount.sh: add reap_stale_nfs_pods()
   function (throttled to every 30 s) that handles two cases invisible
   to the existing fix_mount probe — Case 1: pods stuck in
   CreateContainerConfigError with a stale subPath message (git-server,
   prometheus hit this); Case 2: opt-in Running+Ready pods whose
   in-container write to the NFS volume fails twice in a row (the
   immich-server pattern). Deployed to r0/r1/r2 via Rex.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

0 files changed, 0 insertions, 0 deletions