[Broker] Remove limit on the number of triggers per broker

[lionelvillard]

Problem
The broker controller seems to create a ConfigMap containing all trigger configurations, putting a hard limit on how many triggers can be handled by a single broker.

Persona:
Which persona is this feature for?

Exit Criteria
A measurable (binary) test that would indicate that the problem has been resolved.

Time Estimate (optional):
How many developer-days do you think this may take to resolve?

Additional context (optional)
Add any other context about the feature request here.

This is more a question than a feature request. Feel free to close if I misunderstood how it works.

[pierDipi]

Yes, I've thought about this for a while now.

/assign

cc @slinkydeveloper

[pierDipi]

/area data-plane
/area control-plane

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

[pierDipi]

/remove-lifecycle stale

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

[slinkydeveloper]

I do wonder, @pierDipi and @lionelvillard, do we have an estimate on how large that number is?

[pierDipi]

No that I'm aware of, I can find an upper bound in extreme situations.

[pierDipi]

N = 1200, the contract in json is almost 1MB

n 1200 json 987166 proto 793789

N = 1500, the contract in proto is almost 1MB

n 1500 json 1233766 proto 992089

https://gist.github.com/pierDipi/f2d6775c68d4c6b44b6fbfb6e73050e3

[slinkydeveloper]

@pierDipi thanks for the numbers! @lionelvillard what kind of "numbers" your kafka source operates with usually?

[pierDipi]

Fixed by #3558