I have a single VMAlertmanagerConfig that has a "telegram" receiver:
spec:
receivers:
- name: telegram.status
telegram_configs:
- bot_token:
key: telegram.alerts
name: victoria-metrics-alertmanager-secrets
chat_id: -<redacted> (but it's a signed integer, a group, like -123456)
Since upgrading my operator tor v0.69.0 it cannot reconcile the config with error:
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning ReconciliationError <unknown> victoria-metrics-operator incorrect result configuration, config source=: missing chat_id or chat_id_file on telegram_config
Warning ReconciliationError <unknown> victoria-metrics-operator incorrect result configuration, config source=: missing chat_id or chat_id_file on telegram_config
Warning ReconciliationError <unknown> victoria-metrics-operator incorrect result configuration, config source=: missing chat_id or chat_id_file on telegram_config
Warning ReconciliationError <unknown> victoria-metrics-operator incorrect result configuration, config source=: missing chat_id or chat_id_file on telegram_config
Warning ReconciliationError <unknown> victoria-metrics-operator incorrect result configuration, config source=: missing chat_id or chat_id_file on telegram_config
This is my VMAlertmanager spec:
spec:
configSecret: ""
disableNamespaceMatcher: true
externalURL: <redacted>
image:
tag: v0.32.0
port: "9093"
replicaCount: 1
routePrefix: /
selectAllByDefault: true
templates:
- key: monzo.tmpl
name: vmalertmanager-victoria-metrics-monzo-tpl
Reverting the operator to v0.68.1 restores functionality. It's still possible it's a configuration error on my side but I can't figure out why that would be. The VMAlertmanagerConfig object passes validation just fine.
I have a single
VMAlertmanagerConfigthat has a "telegram" receiver:Since upgrading my operator tor v0.69.0 it cannot reconcile the config with error:
This is my
VMAlertmanagerspec:Reverting the operator to v0.68.1 restores functionality. It's still possible it's a configuration error on my side but I can't figure out why that would be. The
VMAlertmanagerConfigobject passes validation just fine.