-
Notifications
You must be signed in to change notification settings - Fork 1
Known Issues and Limitations
Minh Tu Le edited this page Jun 29, 2025
·
1 revision
-
Session recording is not supported when either the client or the Kubernetes cluster is using the now-deprecated SPDY protocol.
- If your
kubectlclient and Kubernetes cluster are v1.31 and above, you shouldn’t have this issue unless you explicitly disable the followingkubectlfeature control environment variables:KUBECTL_REMOTE_COMMAND_WEBSOCKETSandKUBECTL_PORT_FORWARD_WEBSOCKETS. - If you are connecting to an older cluster with the latest client, you need to enable both feature gates
TranslateStreamCloseWebsocketRequests(added in Kubernetes v1.29) andPortForwardWebsockets(added in Kubernetes v1.30) to enable the newer WebSocket protocol. Otherwise, the streaming protocol will fall back to SPDY. - If your
kubectlclient or Kubernetes cluster is v1.28 and below, the streaming protocol will always fall back to SPDY. - For more detailed information, see this Kubernetes blog post.
- If your
-
kubectl cpmight experience failures on large files (see Kubernetes issue #60140). Usekubectl cp --retriesoption to mitigate the issue.
Copyright © 2025 Twingate.