Sergey Vasilyev

Looks like a known problem (with no issue though, so this one will be it). I've made few attempts to solve this problem previously: #9, and then again in #163...

Can you please show the error and its stack trace?

@Kiddinglife Sorry, I didn't get the part with replicasets. But for polling something in Kopf you can use the `@kopf.on.resume` handlers to start a background thread or an asyncio task:...

@eshepelyuk Cron-based functions can be sufficient for some cases. But they are unaware of Kubernetes resources in any form. First of all, you might have multiple resource to serve, parametrised...

@eshepelyuk Ah, I see. Sorry for misunderstanding. There is no big advantage of using threads over asyncio tasks. Actually, it is a disadvantage — threads are non-stoppable from outside, while...

@eshepelyuk For me, it is not clear if the requested polling is global, or per-resource. I would assume that the intention was to poll the metrics of _specific_ pods of...

Hm. First of all, I am not familiar with Prometheus, so have to read & learn the concepts first, before making any judgements. Nevertheless, despite I understand that Prometheus is...

> … integrate the aiohttp server into the kopf lifecycle. I want to leverage that. That is exactly the point I see as problematic here: `aiohttp` is an internal implementation...

@dlmiddlecote I suggest that we postpone this issue for a while. I drafted few ideas on the cross-object relations & communication ([gist](https://gist.github.com/nolar/8c6233778a30a32fafd7f8d3a55a2cb4); better if read from below). This topic is...

@dlmiddlecote Or, alternatively, we can reduce this issue to filtering only, with `parent` kwarg and dynamic status storage excluded from the criteria. The filtering by existence of `ownerReferences` to a...