Two latent issues found while diagnosing why the May 2026 META vest didn't land: 1. broker-sync-imap CronJob's command was 'broker-sync imap', but the actual CLI subcommand is 'imap-ingest'. Every scheduled run had been failing with 'No such command imap' since day-one. 2. Pod runs as uid=10001 gid=999; PVC /data dir is mode 2775 group=10001. Without fsGroup in the pod's securityContext the pod gets only 'other' (r-x) perms on the dir, so sqlite3 can't create journal/WAL files next to sync.db -- hits 'attempt to write a readonly database'. fsGroup=10001 adds the matching gid to the pod's supplemental groups so writes work. Schwab email-sender regex fix is in broker-sync@d860aef. |
||
|---|---|---|
| .. | ||
| main.tf | ||
| terragrunt.hcl | ||