Sergey Vasilyev

Kopf is designed to work "out of the box" for the majority of cases, i.e. of typically small resources — without any special configuration or external dependencies. For this, it...

Hi. You can probably implement this logic now by defining a semaphore in the on-startup handler and putting it to “memo”. Then, this same semaphore object will be available in...

Hello. No, doing the same as for pykube-ng would be sufficient. For context: pykube-ng (ex-pykube) is there mostly for historic reasons: at some point, Kopf used it as an API...

Thank you! So, there are a few methods beyond the trivial config file. That, combined with its popularity, is a good reason to support kr8s out of the box. A...

Hi. You are welcome! > keeping reference to all kopf-spawned tasks Exactly this is a problem — it is difficult to achieve. First, Kopf spawns tasks for its own needs...

Task naming is available since Python 3.8. Kopf still supports Python 3.7. I’m eagerly waiting for the end-of-life for 3.7 as a milestone, which happens somewhen this summer 2023 if...

> What seems to happen is: request fails because of token expiry -> goes to sleep because of backoff -> while sleeping the session gets closed by vault when invalidating...

Hi. By “Vault”, do you mean Kopf’s Vault (an internal class not exposed to users), or some other vault? If the former (Kopf’s vault), the re-authentication process is already secured...

Maybe. I do not know how Hashicorp Vault & its tokens work. The memo's lifecycle is no longer than the operator's lifecycle: when it exits, the memo is lost. If...

I was overly busy with work & life & German bureaucracy in the past couple of years, but I am slowly getting back to Kopf (not full-time of course). A...