配置 Alertmanager Telegram 频道通知与 OpenBao 凭据投射
yaml / yaml (pull_request) Successful in 32s

This commit is contained in:
2026-09-25 17:09:20 +00:00
parent 6a27adc18d
commit e01f0af4fc
3 changed files with 40 additions and 11 deletions
@@ -0,0 +1,18 @@
apiVersion: external-secrets.io/v1
kind: ExternalSecret
metadata:
name: alertmanager-telegram
namespace: monitoring
spec:
refreshInterval: 1h
secretStoreRef:
kind: ClusterSecretStore
name: openbao
target:
name: alertmanager-telegram
creationPolicy: Owner
data:
- secretKey: telegram_bot_token
remoteRef:
key: k8s/alertmanager
property: telegram_bot_token
@@ -6,6 +6,7 @@ resources:
- vmagent.yaml - vmagent.yaml
- vmalert.yaml - vmalert.yaml
- vmalertmanager.yaml - vmalertmanager.yaml
- alertmanager-external-secret.yaml
- reload-rbac.yaml - reload-rbac.yaml
- rules/vm-health.yaml - rules/vm-health.yaml
- rules/vmagent.yaml - rules/vmagent.yaml
@@ -1,6 +1,4 @@
# Alert router/notifier. Migrated from the retired Compose stack (see Git history), # Telegram token 由 ExternalSecret 从 OpenBao 投射,配置中仅引用文件。
# which currently blackholes everything. Wire real receivers here (email via the
# in-cluster smtp-relay, or a webhook) when you want notifications.
apiVersion: operator.victoriametrics.com/v1beta1 apiVersion: operator.victoriametrics.com/v1beta1
kind: VMAlertmanager kind: VMAlertmanager
metadata: metadata:
@@ -8,19 +6,31 @@ metadata:
namespace: monitoring namespace: monitoring
spec: spec:
replicaCount: 1 replicaCount: 1
secrets:
- alertmanager-telegram
configRawYaml: | configRawYaml: |
route: route:
receiver: blackhole receiver: blackhole
group_by: [alertname, cluster, job, severity]
group_wait: 1m
group_interval: 5m
repeat_interval: 4h
routes:
- receiver: telegram
matchers:
- severity="critical"
group_wait: 10s
repeat_interval: 1h
- receiver: telegram
matchers:
- severity="warning"
receivers: receivers:
- name: blackhole - name: blackhole
# Example email receiver via the in-cluster Postfix relay (smtp-relay/): - name: telegram
# receivers: telegram_configs:
# - name: email - bot_token_file: /etc/vm/secrets/alertmanager-telegram/telegram_bot_token
# email_configs: chat_id: -1003956377923
# - to: '[email protected]' send_resolved: true
# from: 'Alertmanager <[email protected]>'
# smarthost: 'smtp-relay.smtp-relay.svc.cluster.local:25'
# require_tls: false
resources: resources:
requests: requests:
cpu: 25m cpu: 25m