arcodange-org/tools
1
0
Fork 0
Code Issues 3 Pull Requests Actions Packages Projects Releases Wiki Activity

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

Browse Source 
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]>
This commit is contained in:
arcodange
2026-07-08 23:23:07 +02:00
co-authored by Claude Opus 4.8
parent 7a8c8537a5
commit 4005d89c0c
1 changed files with 4 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
prometheus/templates/vault-telegram.yaml
+4
View File
@@ -15,6 +15,10 @@ metadata:
name: alertmanager-telegram name: alertmanager-telegram
namespace: tools namespace: tools
spec: spec:
# Dans le ns tools, VSO exige un vaultConnectionRef explicite (contrairement au ns
# prospection qui hérite d'une connexion par défaut). On pointe la VaultConnection
# `default` déjà présente dans tools (http://hashicorp-vault.tools.svc:8200).
vaultConnectionRef: default
method: kubernetes method: kubernetes
mount: kubernetes mount: kubernetes
kubernetes: kubernetes: