Siebren Z

I've seen this behaviour as well. If i may add reproduce steps: 1. deploy argo-events & argo-workflows as per docs. 2. deploy the goodies at: [my gist](https://gist.github.com/Siebjee/6a666883cefbcff2a091af5a74861eb0) The issue occurs...

Adding to this, when `afterStart: true` is set, this behaviour only gets triggered when a "new" event got created. After attaching a simple go informer to kubernetes to watch what...

I can confirm that v1.5.4 fixes the issue i've described above.

But shouldn't the error be more explanatory :). I didn't submit this issue because it's unsupported, but the error is not clear enough that it isn't supported. In fact it...

I can confirm this issue is still present at: ``` flux: v0.33.0 helm-controller: v0.16.0 image-automation-controller: v0.20.0 image-reflector-controller: v0.16.0 kustomize-controller: v0.20.2 notification-controller: v0.21.0 source-controller: v0.21.2 ```

Heh, I think i missed that part on this cluster :D

@lamida I can't via `helm template..` I can via `helm get manifest` as flux deploys it for me my local `helm template` might not produce the same thing. Both `values.yaml`...

I can confirm 4.2.0 works as intended. I believe my issue was a result of poor lifecycle management on my part.

Been a while since this issue had some activity. But I am hoping it had some work done behind the scenes. Any update on this subject?