Sergey Vasilyev

@asteven That might work as long as the operator has a read/watch permission to the whole cluster. I guess, the problem is that it is not the case. The operator...

I think this is an issue with documentation, which is not clear enough on one particular nuance: When=/field=/other decorator-level filters affect whether Kopf sees the resource or not, i.e. they...

That might be caused by a known issue with yet unknown solution: Kubernetes sometimes “loses” the connection without closing it. Since the connection is technically opened, Kopf does not reconnect...

@francescotimperi The key problem is the existing connection, not a new one. The probe will be showing success since new tcp connections are landing fine. It is the existing connection...

This can also be achieved with `when=` callback filters. If you exclude some issuer(s) from the condition, Kopf will not "see" such resources, so it will not put finalizers on...

Highly likely, yes: timers/daemons require proper termination, for which the operator must ensure that the resource itself remains in the cluster until the termination happened. If there is no finalizer,...

Let’s keep it open so that it remains in my attention. The nearest release is expected to happen with Python 3.12 support once the last blocker (iohttp) is released: #1067;...

Hello. Kopf does not do that, but you can use any other utility that restarts the script when the underlying files change — e.g. [watchdog/watchmedo](https://pypi.org/project/watchdog/), or anything specific to your...

Hi. The answer is: yes and no, depending on the scenario. There is no such functionality to pass the operator's global state to handlers. Especially since there can be several...

Hello. Can you propose the desired syntax for tests, please? I.e., how you would like to express the test scenarios you currently have at hand?