![]() It would surprise me if the behavior of port-forward using the same kubectl version would be different depending on the cluster version.Īlso, can you check whether your pod has restarted while port-forward is running? If that happens, the behavior from kubectl 1.23.0 and later is for the kubectl port-forward command to log an error saying "lost connection to pod" and exit.įor reference, I tried reproducing using kubectl 1.23.1 with a 1.24.0-alpha cluster and also with a 1.21 cluster (this one an EKS cluster). This was behavior of kubectl prior to Can you double-check your kubectl version you were using in both cases? I don't think this problem should be dependent on the cluster version which is why I'm asking. In this case port-forward is still technically running (from a process standpoint on your local machine), but is never able to forward connections again until you stop and restart it. It says it is handling the connection, but it fails every time, so it's not really forwarding them. ![]() OS (e.g: cat /etc/os-release): When testing locally on a Docker node:īut I'm guessing that you continue to get connection refused even though the pod has failed and restarted. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |