Anthony Yeh

Great idea! I thought about something like this but figured I would prioritize emitting events automatically first (#7). Metacontroller knows enough to emit things like: sync hook error, create/update/delete child...

Sorry, I don't understand. Can you give a code snippet or log entries to show what you're trying to do, and what the resulting behavior is?

It sounds like the Voyager Operator is not adding [ControllerRef](https://github.com/kubernetes/community/blob/master/contributors/design-proposals/api-machinery/controller-ref.md#the-three-laws-of-controllers) to the objects it creates. That's an important rule that controllers need to follow in order to maintain the "black...

> so this situation is possible if two+ changes made quickly, handler can processed it almost simultaneously Although there are multiple worker threads, the queue is deduplicated based only on...

Oooh I like that!

To be honest, I haven't figured out a way for Metacontroller to be of much assistance in these scenarios. We had a similar discussion in #107. The common denominator is...

That's a good point. There could be ways to massage your match-making algorithm so there's not one big step of "look at everything and decide everything". For example, you could...

Hm let me see if I can rephrase it to make sure I understand: It sounds like each claim asks for a worker of a particular type, and what you...

FYI if we push forward on a proposal like #98 (prototyping possible API in #142), I think it would make it easy to solve this problem. You could define a...

Ah I think I see what you mean. So, at least if #98 happens, this use case will become feasible: you could have a controller that watches *all* claims as...