Multiple controllers handling same descendant kind

[adriffaud]

Multiple controllers handling same descendant kind

[adriffaud]

Yes sorry! Thanks for the additions!

[mruoss]

Oooh right. Nice catch. I was confused at first as I am using the term "descendant" for the descending object, i.e. the ones created by a controller. If I get you correctly, you have multiple handlers/controllers for the same query. I think it is clear.

[mruoss]

Ooh no now I think I understand. You ARE talking about descendants. So... what stops you from implementing a dispatching controller? This way you wont need to watch the same query multiple times.

[adriffaud]

I am indeed talking about objects created by controllers 🙂
And I guess I was too focused on a controller in a kubernetes sense to think of a dispatching controller at the top 😅
I will try that, thanks!

[mruoss]

Yeah so with Bonny 1.0 controllers are just Pluggable steps. Which makes the whole thing... well... pluggable. I am thinking about adding something like a Bonny.Pluggable.DispatchToOwner step. But ain't there yet with my thinking process.

Instead of using ownerReferences (which technically is a list anyway) I am thinking about adding a label to descendants like example.com/owning-controller: Elixir.MyOperator.Controller.MyController

[mruoss]

@adriffaud On master I have added the Bonny.Pluggable.AddManagedByLabelToDescendants to simplify adding that label to all descendants. You can just plug in into your operator and all registered descendants will have that label.

I'm not proceeding with Bonny.Pluggable.DispatchToOwner as I don't see a simple step handling it all. Instead it would be a "add this step and do that in your controller" etc. So you'll have to implement your dispatching mechanism for now. I see however a neat solution where you would add a "your-operator.com/owning-controller` annotation to all descendants and then use that info to dispatch. But obviously you can also use the ownerReferences field.

[mruoss]

@adriffaud can we close this?