kubectl exec truncates stdout without reporting error about kubernetes HOT 4 OPEN

This sounds like it could be the same problem as #60140 (comment)

This problem should be fixed in server version 1.30+ (actually 1.29+ if you enable the alpha feature). However, I know it is not always simple to upgrade.

As a potential workaround for earlier versions, some people have reported that adding a sleep at the end prevents the output from being truncated.

from kubernetes.

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

from kubernetes.

A sleep does workaround this, generally.

I think this is different from the cp EOF, as in the cp EOF problem the EOF case is detected and successfully reports an error (and I can imagine this happening due to PMTU problems or something, which was mentioned somewhere.

Looks like you're saying the data channel code for this has changed significantly in 1.30 (SPDY->WebSockets or the other way around?) though so that's promising. I'll let you know if I can test or repro on 1.30 if I get the chance to.

If anyone else has a 1.30 environment, would love to see if you can repro the issue there (network congestion is key.)

from kubernetes.

/sig cli

from kubernetes.