kubectl exec timeouts are usually networking or RBAC issues rather than CKS-specific. Confirm the target Pod is Running, that your token or service account has pods/exec permission, and that your client can reach the cluster’s API endpoint. For private clusters, verify Tailscale or Direct Connect is up.
On CKS, exec hangs and timeouts often trace to the Konnectivity tunnel that proxies API server traffic to the kubelet. Check that the konnectivity-agent Pods in the kube-system namespace are healthy, and note that an agent can report Ready while its tunnel is degraded. If the agent is unhealthy or you see proxy errors from konnectivity-server, contact support.
If the issue persists after these checks, contact support.
Server Errors