-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AlertManagerConfig: Add support for the new msteamsv2_configs receiver #7051
Comments
+1 to this. I'm having the same issue |
+1 |
We would need to wait till 0.28 is released 🙂 |
Do you know if this is happening before end of December ? |
Hello, we are having the same issue. Is there any workaround until the 0.28 gets released? |
This was added in alertmanager v0.28.0. Fixes prometheus-operator#7051 Signed-off-by: Marius Schiffer <[email protected]>
This was added in alertmanager v0.28.0. Fixes prometheus-operator#7051 Signed-off-by: Marius Schiffer <[email protected]>
Hi there, just got updated alertmanager to 0.28.0 but issue still persists. I use prometheus stack chart version 68.3.0 with alertmanager v0.28.0 and prometheus operator v0.79.2 and can confirm issue exists. I can see reconciliation error like this However if I will exec into pod, change config directly and then reload alertmanager manually with kill -HUP 1 it will load and validate new conf. Can someone validate it works on their side or it still an issue. Thanks) |
I have the same issue with v68.3.0 kube prometheus stack chart. I also tried installing the alertmanager v0.28.0 chart by itself and encountered the same issue. |
This was added in alertmanager v0.28.0. Fixes prometheus-operator#7051 Signed-off-by: Marius Schiffer <[email protected]>
This was added in alertmanager v0.28.0. Fixes prometheus-operator#7051 Signed-off-by: Marius Schiffer <[email protected]>
This was added in alertmanager v0.28.0. Fixes prometheus-operator#7051 Signed-off-by: Marius Schiffer <[email protected]>
This was added in alertmanager v0.28.0. Fixes prometheus-operator#7051 Signed-off-by: Marius Schiffer <[email protected]>
This was added in alertmanager v0.28.0. Fixes prometheus-operator#7051 Signed-off-by: Marius Schiffer <[email protected]>
This was added in alertmanager v0.28.0. Fixes prometheus-operator#7051 Signed-off-by: Marius Schiffer <[email protected]>
This was added in alertmanager v0.28.0. Fixes prometheus-operator#7051 Signed-off-by: Marius Schiffer <[email protected]>
This was added in alertmanager v0.28.0. Fixes prometheus-operator#7051 Signed-off-by: Marius Schiffer <[email protected]>
Component(s)
AlertManagerConfig
What is missing? Please describe.
I'm running the prometheus-operator v0.72.0, but the latest has the same issue. I have manually set the version of alertmanager to v0.28.0-rc.0 in the "Alertmanager" object. I did this because alertmanager has added support for a new receiver: prometheus/alertmanager#4024 which is highly anticipated. But when I try to use it by adding it to my config (following the steps outlaid in prometheus/alertmanager#3920 (comment) ), it doesn't actually get synced into the alertmanager Pod.
It gets blocked by the prometheus operator which doesn't recognize the field:
level=error ts=2024-10-29T09:50:34.557049663Z caller=klog.go:126 component=k8s_client_runtime func=ErrorDepth msg="sync "prometheus-s ││ tack/prometheus-stack-prometheu-alertmanager" failed: provision alertmanager configuration: failed to initialize from secret: yaml: u ││ nmarshal errors:\n line 27: field msteamsv2_configs not found in type config.plain"
The problem is that prometheus-operator tries to marshal it, and it doesn't exist in the object here:
prometheus-operator/pkg/alertmanager/types.go
Line 99 in d2599cf
But it does here:
https://github.com/prometheus/alertmanager/blob/ff8c09d60174f27850830ceed6be38b3cf86974b/config/config.go#L988
Thanks in advance
Describe alternatives you've considered.
No response
Environment Information.
Environment
Kubernetes Version: 1.29.8
Prometheus-Operator Version: v0.72.0
Alertmanager version: v0.28.0-rc.0
The text was updated successfully, but these errors were encountered: