summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorstaebler <staebler@redhat.com>2017-08-21 15:20:08 -0400
committerstaebler <staebler@redhat.com>2017-08-21 15:20:08 -0400
commite0ed46a691296d5ad8d531eb329e973ab63b8a33 (patch)
tree514e4427ee3a626c95b45fe55222714771272c7d
parentfa3fb913c1870da4dc8f0fb2f28abb99b9b94f55 (diff)
Include "per user" in the comment for Configuration.Limits for the EventRateLimit admission control.
-rw-r--r--contributors/design-proposals/admission_control_event_rate_limit.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/contributors/design-proposals/admission_control_event_rate_limit.md b/contributors/design-proposals/admission_control_event_rate_limit.md
index 5626d8b2..f7180e00 100644
--- a/contributors/design-proposals/admission_control_event_rate_limit.md
+++ b/contributors/design-proposals/admission_control_event_rate_limit.md
@@ -31,18 +31,18 @@ type Configuration struct {
metav1.TypeMeta `json:",inline"`
// Limits to place on events received.
- // Limits can be placed on events received server-wide, per namespace, and
- // per source+object.
+ // Limits can be placed on events received server-wide, per namespace,
+ // per user, and per source+object.
// At least one limit is required.
Limits []Limit `json:"limits"`
}
-// Limit provides configuration for a single type of limit
type Limit struct {
// Type of limit.
// The following are valid values.
// "server": limits are maintained against all events received by the server
// "namespace": limits are maintained against events from each namespace
+ // "user": limits are maintained against events from each user
// "source+object": limits are maintained against events from each source+object
Type string `json:"type"`