New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Set idle and readheader timeouts #103958
Set idle and readheader timeouts #103958
Conversation
/milestone v1.23 |
These values seem reasonable to me. I think clients had to handle getting timeouts either way. /assign @sttts |
/triage accepted |
/retest |
Thanks Jordan! /lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: liggitt, wojtek-t The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/ok-to-test |
/retest |
…958-upstream-release-1.20 Automated cherry pick of #103958: Set idle and readheader timeouts
…958-upstream-release-1.19 Automated cherry pick of #103958: Set idle and readheader timeouts
…958-upstream-release-1.21 Automated cherry pick of #103958: Set idle and readheader timeouts
…958-upstream-release-1.22 [1.22.x] Automated cherry pick of #103958: Set idle and readheader timeouts
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Ensure the apiserver has an opinion about lifetime of keep-alive requests, and sets a timeout on reading incoming request headers (which happens before the
WithRequestDeadline
filter sets a context deadline)Does this PR introduce a user-facing change?
/sig api-machinery
/cc @wojtek-t