Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

kubectl cp to work on stopped/completed pods #454

Open
xellsys opened this Issue Apr 29, 2018 · 13 comments

Comments

Projects
None yet
@xellsys
Copy link

xellsys commented Apr 29, 2018

Status Quo:
The current implementation of kubectl cp requires the container to be running by encapsulating the exec command using the tar binary.

Requirement:
Allow copying files from (possibly also to) a stopped container.

Additional info:
This relates to #58512.
It would also more closely align to the docker cp functionality.
No need for the tar binary in the container anymore.


Background:
My current use case is running helm test with a more sophisticated test set (0 and 1 results do not suffice for analysis) and having a simple way of persisting test results at the end (Jenkins or w/e).
I know there are other solutions but I want to keep my test pod simple (not actively pushing test results to some endpoint or keeping it alive) and would like to avoid extensive configuration of a persistent storage.

@fejta-bot

This comment has been minimized.

Copy link

fejta-bot commented Jul 28, 2018

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@tsuna

This comment has been minimized.

Copy link

tsuna commented Aug 16, 2018

Would be great to have this capability.

@fejta-bot

This comment has been minimized.

Copy link

fejta-bot commented Sep 15, 2018

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@tsuna

This comment has been minimized.

Copy link

tsuna commented Sep 16, 2018

/remove-lifecycle rotten

@seans3

This comment has been minimized.

Copy link
Collaborator

seans3 commented Sep 25, 2018

/kind feature
/sig cli
/area kubectl
/priority P3

@tcoopman

This comment has been minimized.

Copy link

tcoopman commented Sep 28, 2018

Ran into the same issue, but we didn't have to transfer a lot of data. The easiest hack was to tar all the data and base64 encode is and log it to stdout. Then you can get the data out because you can still get the logs for a stopped container.

@fejta-bot

This comment has been minimized.

Copy link

fejta-bot commented Dec 27, 2018

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@tsuna

This comment has been minimized.

Copy link

tsuna commented Dec 28, 2018

/remove-lifecycle stale

@zedtux

This comment has been minimized.

Copy link

zedtux commented Jan 22, 2019

I'm also looking to this feature !

@rafaelaazevedo

This comment has been minimized.

Copy link

rafaelaazevedo commented Feb 8, 2019

this would be great for people who run tests on a kubernetes pod and need to get the reports after

@wjcheng1

This comment has been minimized.

Copy link

wjcheng1 commented Mar 12, 2019

yes would love to have this ability!

@yue9944882

This comment has been minimized.

Copy link
Member

yue9944882 commented Mar 12, 2019

@stmaute

This comment has been minimized.

Copy link

stmaute commented Mar 20, 2019

I also would like to have this feature. Are there any plans to implement this???

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.