kubermatic
Support all four types of limits for the UC EventRateLimit admission controller
Description of the feature you would like to add / User story
KKP supports enabling and configuring the Event Rate Limit, but unfortunately only the "Namespace" type of limits. However, there are four types of limits and they can even be configured at the same time. Please add support for each, and to configure them all at the same time.
Solution details
- End users can configure all four types of limits on the Event Rate Limit admission plugin
- They can configure just one or up to all four in parallel
Alternative approaches
status quo :(
Use cases
Well, what we really need is the "Server" limit, but I think it makes sense to just support all four while at it.
The reason why we need the "Server" limit is because we've had several end users create so many events in such a short time, that they overwhelmed the UC etcd. So now we require our users to "not overwhelm the etcd" but they have no insight into how the etcd is doing and they have no way to limit the events other than trying their best to not create too many events but sometimes something e.g. with Kyverno just goes terribly wrong without being noticed immediately (particularly with those who are not yet familiar with Kyverno but start adapting it) and 4h later etcd is down (yea, slower than ideal disk I/O plays a role in that as well).
Additional information
See also #15090
/label sig/cluster-management /label sig/api /label sig/ui /label customer-request
We need to check if this only needs API/UI modifications.
