# Telegram token 由 ExternalSecret 从 OpenBao 投射，配置中仅引用文件。
apiVersion: operator.victoriametrics.com/v1beta1
kind: VMAlertmanager
metadata:
  name: main
  namespace: monitoring
spec:
  replicaCount: 1
  secrets:
    - alertmanager-telegram
  configRawYaml: |
    route:
      receiver: blackhole
      group_by: [alertname, cluster, job, severity]
      group_wait: 1m
      group_interval: 5m
      repeat_interval: 4h
      routes:
        # dev 必须排第一且不 continue：否则 dev 告警会被后面的 severity 路由送进生产频道。
        - receiver: telegram-dev
          matchers:
            - env="dev"
        - receiver: telegram
          matchers:
            - severity="critical"
          group_wait: 10s
          repeat_interval: 1h
        - receiver: telegram
          matchers:
            - severity="warning"
    inhibit_rules:
      - source_matchers:
          - alertname="KubePodCrashLooping"
        target_matchers:
          - alertname="KubePodFrequentRestarts"
        equal: [namespace, pod, container]
    receivers:
      - name: blackhole
      - name: telegram
        telegram_configs:
          - bot_token_file: /etc/vm/secrets/alertmanager-telegram/telegram_bot_token
            chat_id: -1003956377923
            send_resolved: true
      - name: telegram-dev
        telegram_configs:
          - bot_token_file: /etc/vm/secrets/alertmanager-telegram/telegram_bot_token
            chat_id: -1003651477106
            send_resolved: true
  resources:
    requests:
      cpu: 25m
      memory: 64Mi
    limits:
      cpu: 200m
      memory: 256Mi