Moves the static ftp-scanner-config ConfigMap out of ftp-scanner.yaml
into a configMapGenerator in kustomization.yaml. Values are unchanged
(PASV_ADDRESS=10.2.99.82, ports 21100-21104, scanner, uid/gid 1000).
The content-hash name suffix is kept on purpose: vsftpd templates
pasv_address from PASV_ADDRESS at container start, so a changed value
must roll the pod. With the hash suffix, editing any value renames the
generated ConfigMap, mutates the Deployment pod template, and triggers
an automatic rolling restart. Without it, an IP change (e.g. an LB
re-allocation) would silently leave the pod advertising a stale PASV
address, breaking classic-PASV clients (older Brother scanners) while
EPSV clients keep working.
The Deployment consumes the CM via envFrom.configMapRef, so kustomize's
nameReference transformer rewrites the reference to the hashed name --
verified with `kubectl kustomize` (ftp-scanner-config-6d2597bt4d).
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
k.rennerandClaude Opus 4.8