Abu Kashem e416c9e574 apiserver: plumb context with request deadline ...

- as soon as a request is received by the apiserver, determine the
  timeout of the request and set a new request context with the deadline.
- the timeout filter that times out non-long-running requests should
  use the request context as opposed to a fixed 60s wait today.
- admission and storage layer uses the same request context with the
  deadline specified.

we use the default timeout enforced by the apiserver:
- if the user has specified a timeout of 0s, this implies no timeout on the user's part.
- if the user has specified a timeout that exceeds the maximum deadline allowed by the apiserver.

2021-01-28 14:15:04 -05:00

..

admission_test.go

Merge pull request #95012 from nodo/add-namespace-to-post-based-namespace-creation

2020-10-01 17:37:20 -07:00

apiserver_handler_test.go

unit and integration tests

2020-11-18 12:46:20 -08:00

broken_webhook_test.go

automated refactor

2020-03-05 14:59:46 -08:00

BUILD

generated

2020-11-18 12:48:26 -08:00

client_auth_test.go

automated refactor

2020-03-05 14:59:46 -08:00

load_balance_test.go

automated refactor

2020-03-05 14:59:46 -08:00

main_test.go

…

reinvocation_test.go

cleanup: no need nil check before range

2020-04-27 22:12:12 +08:00

timeout_test.go

apiserver: plumb context with request deadline

2021-01-28 14:15:04 -05:00