WhatBrokeToday
FAQ
Today's Trends
highInvestigatingKubernetes

Kubernetes kubectl port-forward Exits and Closes Local Listener on Server Workload RST

  1. Investigating(current)
  2. Trending(upcoming)
  3. Workaround available(upcoming)
  4. Resolved(upcoming)

Executive summary

When a pod resets a forwarded connection via a TCP RST, kubectl port-forward exits with an error and terminates the local listener. This causes all concurrent and subsequent connections through the same port-forward to fail with connection refused.

No verified workaround yet

None of the linked reports describe a mitigation. Follow this incident to hear when one appears.

Official fix
Technical root cause

Under active investigation. No report has identified a root cause yet.

Evidence

1 report · 1 GitHubShow
  1. [1]
    GitHub First report
    portforward improperly closes local listener in response to server workload RST, breaking all subsequent connections(opens GitHub issue in a new tab)

    What happened? When the pod side resets one forwarded connection (TCP RST on the pod-local loopback hop), the container runtime reports an error for that connection and kubectl port-forward then exits with error: lost connection to pod. The local listener terminates, so every other connection through the same port-forward, and every later one, fails with connection refused. E1102 14:33:01.870223 portforward.go:424] "Unhandled Error" err="an error occurred forwarding 18445 -> 8443: error…

    by ringerc 0upvotes 12comments

Timeline

  1. First report on GitHub issue

    portforward improperly closes local listener in response to server workload RST, breaking all subsequent connections

    Source