You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that in kubectl cp that it looks like the tar.Read just uses a byte stream to capture where it left off and continue. Could that logic be replicated here? Basically just create an io pipe and keep track of where we are in the bytes? Also sorry if this is out of left field, I'm new to contributing to Kubernetes in any capacity.
Describe the bug
cpFromPod
/cpToPod
silently fail on larger files, resulting in incomplete files.** Client Version **
0.20.0
** Server Version **
1.25.7+rke2r1
To Reproduce
upload a larger file, at least 200MB. The kubernetes issue has gone into detail about network settings a.s.o.
Expected behavior
cpFromPod
/cpToPod
should try to upload the whole file or error out on premature disconnect.Environment (please complete the following information):
Additional context
Has been identified and 'fixed' in
kubectl cp
kubernetes/kubernetes#60140 with the--retries
flag.The text was updated successfully, but these errors were encountered: