Sergey Vasilyev

That is not expected. However, it is difficult for me trying to help without at least the operator’s logs (with “-v” enabled), not to mention a reproducible snippet (with all...

[email protected]

Sorry, I probably cannot help you with the state machines and transitions here. > I looked into in-memory indexing, but with the indices being read-only it is not possible to...

Hello. Thanks for sharing your experience with the framework and this feature! That is always highly valuable. Regarding the integration: I cannot say what is considered a good way FastAPI...

Hello. The daemons are stopped when the operator's process loses its active role and pauses. The daemons themselves can notice that by checking the stopping flag's reason as `(stopped.reason &...

> But... in the case of an active peer becoming passive, how would I cancel the task? You cannot. Peering status is not reported to handlers, so they cannot pass...

Can standard synchronisation primitives work for this task? ```python import kopf import time import threading # or asyncio, if you wish @kopf.on.create('kopfexamples') @kopf.on.resume('kopfexamples') def init_primitives(memo, **_): memo.cond = threading.Condition() memo.delete_me_at...

If kubectl does not change the resource, Kopf will never know that anything was attempted at all. One hack to think about is to ensure the changes on every kubectl...

Thanks for asking. It is a good question. First, please clarify if those are indeed events missed or changes not detected — on.event vs. on.create/update/delete handlers. There is a known...

Thanks for this information. I've updated the #641 title to also refer to regular handlers, not only sub-handlers. The issue affects them all. Just to clarify: Kopf does not skip...