Allow the eventRecordQPS setting to be set. (#6880)
* Allow the eventRecordQPS setting to be set. The eventRecordQPS parameter controls rate limiting for event recording. When zero, unlimited events can cause denial-of-service situations. For my situation, I don't need more than a setting of "5". This change allows me to configure the setting before creating the cluster. * Allow the eventRecordQPS setting to be set. The default settings (see types.go) is five. So, this change does not affect the cluster provisioning. However, it does allow for the setting to be changed.
This commit is contained in:
parent
9cf5dd0291
commit
fefcb8c9f8
2 changed files with 7 additions and 0 deletions
|
@ -91,3 +91,6 @@ tlsCipherSuites:
|
||||||
- {{ tls }}
|
- {{ tls }}
|
||||||
{% endfor %}
|
{% endfor %}
|
||||||
{% endif %}
|
{% endif %}
|
||||||
|
{% if kubelet_event_record_qps %}
|
||||||
|
eventRecordQPS: {{ kubelet_event_record_qps }}
|
||||||
|
{% endif %}
|
||||||
|
|
|
@ -534,3 +534,7 @@ host_architecture: >-
|
||||||
{%- else -%}
|
{%- else -%}
|
||||||
{{ ansible_architecture }}
|
{{ ansible_architecture }}
|
||||||
{%- endif -%}
|
{%- endif -%}
|
||||||
|
|
||||||
|
# Sets the eventRecordQPS parameter in kubelet-config.yaml. The default value is 5 (see types.go)
|
||||||
|
# Setting it to 0 allows unlimited requests per second.
|
||||||
|
kubelet_event_record_qps: 5
|
||||||
|
|
Loading…
Reference in a new issue