Though, after some time the performance degrades to what was described above. If stop the port forwarding process (which, btw, doesn't respond to Ctrl-C, I have to do kill -9) and retry the whole process the same thing happens again (and i manage to upload another few layers).ĮDIT: Interestingly, after a system restart the docker push command works a bit longer before slowing down (and there aren't any errors in the kubectl port-forward commands output). The push refers to repository ģca254258b97: Pushing 34.24MB $ docker push localhost:5000/taskservice:latest
We have multiple HTTP requests being made at any given time on this port-forward connection.Ĭlient Version: version.Info
#Kubernetes portforward how to
How to reproduce it (as minimally and precisely as possible):Ĭonnect via port-forward and transfer ~5 mb over several minutes. No error messages or major degradation in transfer rate. These errors are oftentimes followed by timeout messages but necessarily immediately:Į0225 15:22:30.454203 26392 portforward.go:353] error creating forwarding stream for port 9090 -> 9090: Timeout occured I see the following error message initially:Į0225 15:20:06.212139 26392 portforward.go:363] error copying from remote stream to local connection: readfrom tcp6 :9090->:57794: write tcp6 :9090->:57794: write: broken pipe There seems to be a correlation between error rate and the amount of data being transferred.
Kubectl port-forward -namespace monitoring deployment/cost-monitor 9090 I am able to connect to this pod (using the following command) but then start getting broken pipe error messages after maintaining a connection for what is typically 30-60s. We have a pod running in our k8s cluster that I connect to via kubectl port-forward.
0 kommentar(er)
