First off I'll say I'm not sure if this is a bug or if we were using the notification-controller incorrectly
From version v1.8.0 of the notification-controller, a change was made in #1231 to skip sending events if the event contains kustomize.toolkit.fluxcd.io/commit_status in the metadata.
Until 1.8.0 these events would be sent to the Generic Provider. I do see that previously the skip commit metadata updates were filtered out in each notifier rather than directly in the notifiers themselves.
Somewhat related is that the logs appear to show that the event was sent to the provider. Whereas other events which aren't sent have the message "discarding event, ...".
{"level":"info","ts":"2026-04-10T10:29:58.421Z","logger":"event-server","msg":"dispatching event","eventInvolvedObject":{"kind":"Kustomization","namespace":"flux-system","name":"my-kustomization","uid":"c0664df8-21db-453c-a628-31d09cb35821","apiVersion":"kustomize.toolkit.fluxcd.io/v1","resourceVersion":"244318194"},"message":"Reconciliation finished in 449.617964ms, next run in 24h0m0s"}
First off I'll say I'm not sure if this is a bug or if we were using the notification-controller incorrectly
From version v1.8.0 of the notification-controller, a change was made in #1231 to skip sending events if the event contains
kustomize.toolkit.fluxcd.io/commit_statusin the metadata.Until 1.8.0 these events would be sent to the Generic Provider. I do see that previously the skip commit metadata updates were filtered out in each notifier rather than directly in the notifiers themselves.
Somewhat related is that the logs appear to show that the event was sent to the provider. Whereas other events which aren't sent have the message "discarding event, ...".
{"level":"info","ts":"2026-04-10T10:29:58.421Z","logger":"event-server","msg":"dispatching event","eventInvolvedObject":{"kind":"Kustomization","namespace":"flux-system","name":"my-kustomization","uid":"c0664df8-21db-453c-a628-31d09cb35821","apiVersion":"kustomize.toolkit.fluxcd.io/v1","resourceVersion":"244318194"},"message":"Reconciliation finished in 449.617964ms, next run in 24h0m0s"}