Sergey Vasilyev

I think, it is possible. Though it was never an intended use-case, probably can be broken in the future, and the consequences of doing so are unknown. One problem that...

As far as I remember, there are few function calls available in 3.7 only: * `contextvars` module — the only tricky part to back-port (kind of thread-local storage, but for...

**UPD:** I was thinking on this topic for couple days. And came to the conclusion that it is better to keep Kopf with Python 3.7+, and to not port it...

@chainhead Is it a cluster-scoped CRD or namespace-scoped? Can you please show the CRD's YAML and `pod.yaml`? In any case, it seems like an issue with `kubernetes` client library, not...

For custom resources — yes (when it is namespace-scoped). But here, you create a pod, and this pod needs its own namespace specified. Pods cannot be cluster-scoped, they **must** be...

Thanks for reporting. Currently, only raw dicts are supported. The classes of other libraries are not yet supported. Though, it would be a good addition for this specific toolkit —...

@janvdvegt That is correct: Kubernetes API clients are not used in Kopf. Only `aiohttp` is used — for API communication (low-level). However, Kopf has slightly extended behaviour if `kubernetes` and/or...

@mzizzi Do you mean the in-memory event accumulation, aggregation, and then posting only the aggregated events every few seconds/minutes/events? Or is this also about the event patching with "lastTimestamp", "count",...

I am not sure that I got the idea right. So the answer may be wrong or irrelevant. But this is how I would approach it: Since there are pods...

Also, `kopf run handlers.py` with an empty file (completely empty or just with no handlers) should say something meaningful, like "I have nothing to do". Currently, it runs (and does...