- Earth, Milky Way
- https://aaronriedel.de
- Joined on
2021-12-08
Alerting: use telegram_bot_token when Alertmanager v0.26.0 is out
done with b7eb2dc405e737291cc958f112047cbfbfa33380
Alerting: use telegram_bot_token when Alertmanager v0.26.0 is out
b7eb2dc405
Merge pull request 'Move Alertmanager config back into helm' (#14) from alertmanager-0-26-0 into main
c6b97ac1e8
update kube-prometheus-stack to 51.0.3
94c2a34aac
try to fix prometheus 2
778306127f
try to fix prometheus
ffaf6a079e
put alertmanager config back into helm values
Move Alertmanager config back into helm
Create Longhorn with multiple disks
CiliumIdentity needs to be excluded/ignored in argocd for deployments to become healthy
waiting for us to switch to cilium again
Alerting: use telegram_bot_token when Alertmanager v0.26.0 is out
created MR with my changes: yolokube/core-deployments#14
Move Alertmanager config back into helm
94c2a34aac
try to fix prometheus 2
778306127f
try to fix prometheus
ffaf6a079e
put alertmanager config back into helm values
Alerting: use telegram_bot_token when Alertmanager v0.26.0 is out
Fixed 2 of those issues with 94c2a34aac7c478a7e4dd2850ba3c12bd7d6f222
bot_token_file is not supported currently by the prometheus operator:
Alerting: use telegram_bot_token when Alertmanager v0.26.0 is out
`│ 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 …