cjbaar

OK, well I am trying various cases with the `on.update()` with `field` handler, and so far can't get it to misfire again. So before we dig too deeply in the...

Ok... so I am encountering a missed trigger again. Here is the definition of the handler that is not firing. ``` @k8s.kopf.on.resume( 'service', annotations={'service-mesh.operator.ccp/component-sync': 'update'}, param='resume' ) @k8s.kopf.on.create( 'service', annotations={'service-mesh.operator.ccp/component-sync':...

Thanks, as always, for the quick reply. When the reconcile process for a given Service completes, it patches the annotation value back to 'ok'. So the starting value should always...

There is only one configmap currently involved; the dev cluster has about 35 services. I will take a look at the indexing. I guess I was generally trying to avoid...

Also, not to confuse the issue, but I turned on debugging for some of my logging to try to follow this closer, and now I see evidence that an `on.create()`...

So... basically for my patch action, I am excepting the `on.update()` to fire, but instead an `on.create()` is attempted, and denied by a filter. But, this happens only part of...

There should be no "new" services at this point. We aren't creating additional resources while the operator is running. So based on debug the `on.create()` handler is attempting to run...

Patching is done using the k8s client `patch_namespaced_service`. It is my understanding that this only supports a "strategic merge patch", and since annotations are a map (dict), I thought other...

FYI, other annotations that the operator does not interfere with appear to be intact.

Thanks again. I will try tweaking the batch-window and see if that helps. It seems very likely this is some kind of timing issue with the two patch events. As...