Alerting: use telegram_bot_token when Alertmanager v0.26.0 is out #2
Labels
No labels
state
stale
state
to-do
state
waiting
system
argo
system
cni
system
dashboard
system
ingress
system
monitoring
system
storage
system
woodpecker
type
bug
type
enhancement
type
update
type
dependency-dashboard
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: yolokube/core-deployments#2
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
We are currently using a self built alertmanager container that is built here. Once the version 0.26 comes out and this commit is included we can switch back to the default tag. For that the prometheus values file needs to be adjusted.
switch back to stable alertmanager imageto use telegram_bot_token when Alertmanager v0.26.0 is outWith commit
e63707d16c
I moved back to the official image. The entire alertmanager config is in a secret for now. Once Version v0.26.0 comes out we can put the config back into the values and only have the bot token as a secret.use telegram_bot_token when Alertmanager v0.26.0 is outto Alerting: use telegram_bot_token when Alertmanager v0.26.0 is outAlertmanger v0.26.0 is out now!
basically fixed with
778306127f
andffaf6a079e
However argocd refuses to apply the new values
│ eus-alertmanager\" failed: provision alertmanager configuration: failed to initialize from secret: yaml: unmarshal errors:\n line 16: field bot_token_file not found in type config.plain\n line 35: field storage not found in type config.plain\n line 45: field useExistingSecret not found in type config.plain" │
Fixed 2 of those issues with
94c2a34aac
bot_token_file is not supported currently by the prometheus operator:
https://github.com/prometheus-operator/prometheus-operator/issues/5858
created MR with my changes: yolokube/core-deployments#14
done with
b7eb2dc405