Alan Silva

@dhoppe I'd need to retest but do remember a small increase in execution time. However, I do believe the added flexibility is well worth the added couple of seconds.

This definitely threw me off. I was about to open a bug for the `debug` flavour before I found this issue.

I just ran into this issue. Deleting the `KopfFinalizerMarker` did the trick for me as well. @akojima Did you end up opening a separate bug? If not, I'll try to...

Yeah, sorry, I could have definitely been clearer. So, I tried the following things: ## `on.delete` _with_ finalizers (normal use case) ``` @kopf.on.delete('', 'v1', 'configmaps', when=kopf.all_([label_is_satisfied, resource_is_desired])) @kopf.on.delete('', 'v1', 'secrets',...

Hey @trishul5, did you try using `on.event()` handlers? I had a similar question in https://github.com/nolar/kopf/issues/701 and that's what did it for me.

> No, I haven't tried that but it looks promising. > For the on.event() filters, can I specify a filter that will filter by annotation? What I want to do...

Hmm, I'm afraid I don't know the answer to that one. Haven't seen that behaviour on my end, kopf is fairly quiet for me. You're not running with `--debug` or...

Sorry for jumping in, was following this discussion with interest and just wanted to make sure I understood something. We're talking about the `kopf.zalando.org/last-handled-configuration` annotation that kopf adds to handle...

> Maybe kopf cold be run as a CronJob or Job ? :)) Hahaha, you joke about that but... The issue is that the Helm chart the users of my...

> Is the chart external and they include your docker ? Exactly this. It's actually the Grafana Helm chart. It used another image, but it has had issues for half...