- Ya
- 3 Agosti 2026, 04:35 UTC
- Mwandishi
- Kamo
- Ahadi ya
- fbfa3d8
The new EmailService pod has been in CrashLoopBackOff since 16e8a05 — 22 restarts, never once started. snakeyaml raises DuplicateKeyException on a repeated top-level key, and I added a second `kamo:` block for the sender-avatar kill switch when one already existed at the top of both the packaged application.yml and the k8s configmap. It fails in **************** before any bean is created, so none of the usual startup diagnostics appear. The old replicaset kept serving throughout, so mail never went down and nothing looked wrong from outside — but the avatar endpoints this was added for have never actually been live. Both files fixed by merging into the single existing `kamo:` mapping. YAML has no merge semantics for repeated keys; the second one is an error, not an override. Worth noting the configmap is the copy that matters — it is what the deployment mounts, and it was the one the reported line number pointed at. Fixing only the packaged application.yml would have changed nothing.