Copy local file to pod using tar

[lazarkrstic]

No description provided.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: lazarkrstic / name: Lazar Krstić (86b15a5)

[k8s-ci-robot]

Welcome @lazarkrstic!

It looks like this is your first PR to kubernetes-client/csharp 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-client/csharp has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[tg123]

thanks

I will make inner websocket chunked

[tg123]

/LGTM

[lazarkrstic]

Can you remove label invalid-commit-message , I amended my privious git message

[tg123]

do not put # in message, just remove it and push -f

[tg123]

/LGTM

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lazarkrstic, tg123

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [tg123]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[cody-malcolm]

@lazarkrstic Thanks for doing this. When I use this example, the file is copied to the pod successfully, but then the thread blocks on the error checking starting at line 96...specifically being blocked by streamReader.EndOfStream. I have tried various other ways to perform the same check (such as ReadLine, Read, or stdError.Length) and they all block. If I remove the error check entirely, it will block in Kubernetes.Exec.cs at await errorReader.ReadToEndAsync().ConfigureAwait(false);. Do you know why this might be happening or what can be done to fix it? I'm out of ideas to fix it. Thanks in advance.

[tg123]

@cody-malcolm what is your base image?

only ubuntu' tar passed the test

see comment here

csharp/tests/E2E.Tests/MinikubeTests.cs

Line 654 in fd3931c

// Image = "busybox", // TODO not work with busybox

[cody-malcolm]

@tg123 We are using node:16.15.0-alpine base image. Based on Alpine Linux.

Edit: After some digging, I discovered this uses busybox, and the implementation doesn't work with the busybox version of tar. So that explains the issue.