You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Tom Meadows 0586d5d40d k8s-operator/sessionrecording: gives the connection to the recorder from the hijacker a dedicated context (#17403) ... The hijacker on k8s-proxy's reverse proxy is used to stream recordings to tsrecorder as they pass through the proxy to the kubernetes api server. The connection to the recorder was using the client's (e.g., kubectl) context, rather than a dedicated one. This was causing the recording stream to get cut off in scenarios where the client cancelled the context before streaming could be completed. By using a dedicated context, we can continue streaming even if the client cancels the context (for example if the client request completes). Fixes #17404 Signed-off-by: chaosinthecrd <tom@tmlabs.co.uk>		6 months ago
..
fakes	k8s-operator,sessionrecording: fixing race condition between resize (#16454)	9 months ago
spdy	k8s-operator,sessionrecording: fixing race condition between resize (#16454)	9 months ago
tsrecorder	k8s-operator,sessionrecording: fixing race condition between resize (#16454)	9 months ago
ws	all: use Go 1.20's errors.Join instead of our multierr package	7 months ago
hijacker.go	k8s-operator/sessionrecording: gives the connection to the recorder from the hijacker a dedicated context (#17403)	6 months ago
hijacker_test.go	k8s-operator/sessionrecording: gives the connection to the recorder from the hijacker a dedicated context (#17403)	6 months ago