Some resources always send a notification

[mbrancato]

Is there a way that we can prevent notifications for "changes" to resources that are not being changed? I don't know the best way to actually determine if changes were made, maybe this is an upstream issue.

It might be that this is caused by the kustomize.toolkit.fluxcd.io/checksum label. Is there any way to ignore this since we get flooded with objects being changed when they are not.

[heschlie]

The ImagePolicy resource also spams notifications. I feel like most folks would expect notifications to only be "Hey this thing changed" as right now those get lost in all of the "Hey here is the same message I posted 5 minutes ago".

[uderik]

I have not found a normal solution to send messages only for new image releases via alert, ImagePolicy spam message on every scan

[stefanprodan]

Policy spam issue tracked here: https://github.com/fluxcd/image-reflector-controller/issues/166

[pkit]

Policy spam issue tracked here: fluxcd/image-reflector-controller#166

I'm not sure how should I track which resources spam and which are not? What I see is that after upgrade to flux = 0.19.1 from 0.17.2 some resources started spamming with "green" configured messages. And I have no indication in logs what's causing that. Namely

Service/projectcontour/envoy configured
Deployment/default/external-dns configured

[stefanprodan]

@pkit please open an issue in kustomize-controller repo, if you could provide a repo with the contour and external-dns I will try to replicate the bug and fix it. Thanks!