fix(alerting): VaultAuth Telegram exige vaultConnectionRef dans le ns tools #10

Merged

arcodange merged 1 commits from arcodange/am-telegram-fix into main

2026-07-08 23:23:36 +02:00

Author	SHA1	Message	Date
arcodangeandClaude Opus 4.8	4005d89c0c	fix(alerting): VaultAuth Telegram exige vaultConnectionRef dans le ns tools Helm Charts / Library charts tool (push) Has been skipped Details Helm Charts / Detect changed charts (push) Successful in 16s Details Helm Charts / Detect changed charts (pull_request) Successful in 15s Details Helm Charts / Library charts tool (pull_request) Has been skipped Details Helm Charts / Application charts pgcat (push) Has been skipped Details Helm Charts / Application charts pgcat (pull_request) Has been skipped Details VSO refuse un VaultAuth sans vaultConnectionRef dans le ns tools (« vaultConnectionRef must be set on resources in the "tools" namespace »), contrairement au ns prospection qui hérite d'une connexion par défaut. On référence la VaultConnection `default` déjà présente dans tools. Sans ça, le Secret alertmanager-telegram n'est jamais synchronisé et le pod Alertmanager reste bloqué sur le montage manquant. Co-Authored-By: Claude Opus 4.8 <[email protected]>	2026-07-08 23:23:07 +02:00