Detections
Analytics

1.2.26 Ensure that the --request-timeout argument is set as appropriate

Warning! Audit Deprecated

This audit has been deprecated and will be removed in a future update.

View Next Audit Version

Information

Set global request timeout for API server requests as appropriate.

Rationale:

Setting global request timeout allows extending the API server request timeout limit to a duration appropriate to the user's connection speed. By default, it is set to 60 seconds which might be problematic on slower connections making cluster resources inaccessible once the data volume for requests exceeds what can be transmitted in 60 seconds. But, setting this timeout limit to be too large can exhaust the API server resources making it prone to Denial-of-Service attack. Hence, it is recommended to set this limit as appropriate and change the default limit of 60 seconds only if needed.

Impact:

None

Solution

Edit the API server pod specification file /etc/kubernetes/manifests/kube-apiserver.yaml and set the below parameter as appropriate and if needed. For example,

--request-timeout=300s

Default Value:

By default, --request-timeout is set to 60 seconds.

See Also

https://workbench.cisecurity.org/files/2968

Item Details

References: CSCv6|14.6, CSCv7|14.9

Plugin: Unix

Control ID: b73b9b58232a1f52669eec3b6ac355d576aa46dcb7a1bca81a9bc34af227d5f3