f883f17313
IIUC, before using the translator handler, the ping data can be delivered from the client to the runtime side since kube-apiserver does not parse any client data. However, with WebSocket, the server responds with a pong to the client without forwarding the data to the runtime side. If a proxy is present, it may close the connection due to inactivity. SPDY's PingPeriod can help address this issue. Signed-off-by: Wei Fu <fuweid89@gmail.com> Co-authored-by: Antonio Ojea <aojea@google.com> (cherry picked from commit dc59c0246fb407dcf035afc224f63fcf0da8244e) Signed-off-by: Wei Fu <fuweid89@gmail.com> Kubernetes-commit: e8b0252a41295ad09e44f638dde9f76e1c0accf4 |
||
|---|---|---|
| .. | ||
| apihelpers | ||
| dryrun | ||
| feature | ||
| flowcontrol | ||
| flushwriter | ||
| notfoundhandler | ||
| openapi | ||
| peerproxy | ||
| proxy | ||
| shufflesharding | ||
| version | ||
| webhook | ||
| wsstream | ||
| x509metrics | ||