Sergey Vasilyev

I am not that experienced with Kubernetes management and low-level optimizations, so I have no opinion on this. The referred issue seems interesting though. Keep in mind that if you...

No, Kopf only sends the patch, i.e. 1x size. The API server responds with the patched object, so 2x the size. Yes, your CR size is small, the size should...

Thanks for asking. This default behavior (requiring the credentials) is for Kopf to work "out of the box" for its main purpose — the operator framework. I first thought that...

Hello. The filtering callback should be called on every new event that arrives from the Kubernetes watch-stream — because it is implied that the arbitrary condition can change any time...

It’s interesting. My first assumption would be that apiservers return something which is not json (perhaps, html). Which is weird on its own, but let’s check. Can you please execute...

Hm. The response itself looks good and parseable. My next assumption would be that it is something with the HTTP/TCP streams: e.g. incomplete reads in the underlying aiohttp, or maybe...

Hello. Sorry, I probably didn’t get what is the question or a supposed behavior alternative to the existing one. Generally, you are right: with optional=True, there are no finalizers, and...

Thanks for clarifying. Indeed, I could reproduce this locally with kubectl alone. I think I know what causes it. When a resource is deleted with a finalizer, `.metadata.deletionTimestamp` is set....

Sorry, I cannot help here with the operator's logic of status updates without a repro or logs. Both cases of patching —from on.update & on.event— should work. If you see...

Hm. That is strange. Thanks for reporting. The only suspicious place in this regard is `WebhookContextManager` & `WebhookContextManagerMeta`, which are the parents of `kopf.WebhookServer`. It is possible that they cause...