client-go: HTTP port-forward broke on client terminates
Situation
- Components are connected as Go server -> port-forward -> iOS Client
- Using chunked transfer encoding to download large movie file from Server to iOS
problem
When iOS client exits with SIGKILL (i.e. restart app from Xcode), the port forward emits an error
E1119 14:59:19.967004 9736 portforward.go:303] error copying from remote stream to local connection: readfrom tcp4 127.0.0.1:8888->127.0.0.1:35390: write tcp4 127.0.0.1:8888->127.0.0.1:35390: write: broken pipe
It is ok, but after this error, all connections to portforward are rejected with timeout.
E1119 15:15:07.167402 9736 portforward.go:271] error creating error stream for port 8888 -> 8888: Timeout occured
Expected behavior
portforward accepts the following requests after broken pipe.
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Reactions: 14
- Comments: 29 (1 by maintainers)
Experience same error using Kubernetes in Azure when opening a tunnel to the cluster with az aks browse. Works for a time, then starts to get this error and the tunnel becomes very unstable.
@s1dequest Thanks for the suggestion, but our certs are fine. port-forward always works, its just not stable
Can confirm the same on my AKS cluster on azure. The deployment / upgrade goes through and deployment is runned. But the Release pipeline is marked as failed.
4383 portforward.go:363] error copying from remote stream to local connection: readfrom tcp4 127.0.0.1:43163->127.0.0.1:56726: write tcp4 127.0.0.1:43163->127.0.0.1:56726: write: broken pipe