You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Sharing EventSource for Dependent Resource Based on Name #2408
DependentResource creates event sources, the problem is when there are dependent resource of same type and want to share event source. In this case, currently the event source needs to be explicitly created (not by the DR), and set to the dependent.
One alternative would be to handle this by name, so that the informer created by a dependent resource would have the same name as an already registered event source (from other DR) , the controller would just set the already existing ES to the DR.
The downside of this is that, if those informers would have different configuration this would not be detected.
This is especially important so we able to have more dependent resources with activation condition with same type sharing ES.
changed the title [-]Creating and Sharing EventSource for Dependent Resource Based on Name[/-][+]Sharing EventSource for Dependent Resource Based on Name[/+]on May 28, 2024
Activity
[-]Creating and Sharing EventSource for Dependent Resource Based on Name[/-][+]Sharing EventSource for Dependent Resource Based on Name[/+]csviri commentedon Jun 28, 2024
Was thinking more about this, since sharing by name already works for activation condition, see:
#2454
This is actually not that important, and might be even confusing. So if no objections would close the issue with won't fix.