Alerting: use telegram_bot_token when Alertmanager v0.26.0 is out #2

Closed
opened 2023-04-20 05:12:56 +02:00 by aaron · 7 comments
Owner

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.

We are currently using a self built alertmanager container that is built [here](https://git.ar21.de/aaron/alertmanager-build). Once the version 0.26 comes out and [this commit](https://github.com/prometheus/alertmanager/commit/6c9c58015e051cda5fe8f48e6918a4c7646d5538) is included we can switch back to the default tag. For that the prometheus values file needs to be adjusted.
aaron changed title from switch back to stable alertmanager image to use telegram_bot_token when Alertmanager v0.26.0 is out 2023-06-21 04:19:02 +02:00
aaron added the
type
enhancement
system
monitoring
labels 2023-06-21 04:19:24 +02:00
Author
Owner

With 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.

With 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.
aaron changed title from use telegram_bot_token when Alertmanager v0.26.0 is out to Alerting: use telegram_bot_token when Alertmanager v0.26.0 is out 2023-06-21 04:26:09 +02:00
Author
Owner

Alertmanger v0.26.0 is out now!

Alertmanger v0.26.0 is out now!
aaron added this to the Prod ready project 2023-08-29 17:12:57 +02:00
Author
Owner

basically fixed with 778306127f and ffaf6a079e

However argocd refuses to apply the new values

basically fixed with 778306127fb86162ddae58433579e30ae09a048d and ffaf6a079e64f210a804c9712eacb76fd8cff7df However argocd refuses to apply the new values
Author
Owner

│ 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" │

`│ 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" │`
Author
Owner

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

Fixed 2 of those issues with 94c2a34aac7c478a7e4dd2850ba3c12bd7d6f222 bot_token_file is not supported currently by the prometheus operator: https://github.com/prometheus-operator/prometheus-operator/issues/5858
Author
Owner

created MR with my changes: yolokube/core-deployments#14

created MR with my changes: yolokube/core-deployments#14
aaron added the
state
waiting
label 2023-08-31 00:42:47 +02:00
Author
Owner

done with b7eb2dc405

done with b7eb2dc405e737291cc958f112047cbfbfa33380
aaron closed this issue 2023-09-15 01:45:32 +02:00
tom removed the
state
waiting
label 2024-01-29 12:10:58 +01:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: yolokube/core-deployments#2
No description provided.