Feature Request: cp

[saada]

Offer an API equivalent to kubectl cp.

Suggested design...

import fs from 'fs'
const pods = await deployment.getPods()
const readStream = fs.createReadStream('myfile.txt')
await pods[0].cp(readStream, "/tmp/myfile.txt")

// or from an inline string
import { Readable } from 'stream'
const inlineStream = new Readable()
const inlineFile = `
#!/bin/bash
echo hello world
`
inlineFile.split('\n').forEach(line => inlineStream.push(line))
inlineStream.push(null)
await pods[0].cp(inlineStream, "/tmp/myfile.txt")

[brendandburns]

fwiw, cp is just a wrapper on top of exec.

I implemented this for Java here:

kubernetes-client/java#375

I'd gladly take an equivalent PR (with tests!) for TypeScript, or if I get to it, I'll send a PR...

[saada]

Related: #67

[vaishnavipamulapati]

I would like to work on this issue

[brendandburns]

@vaishnavipamulapati go for it, it's yours.

[fejta-bot]

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

[fejta-bot]

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

[brendandburns]

/remove-lifecycle rotten

[fejta-bot]

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

[fejta-bot]

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

[drubin]

/remove-lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

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

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

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

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[drubin]

/reopen
/remove-lifecycle rotten
/lifecycle frozen

[k8s-ci-robot]

@drubin: Reopened this issue.

In response to this:

/reopen
/remove-lifecycle rotten
/lifecycle frozen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[vip30]

Can we close this issue?

[brendandburns]

Closing since #482 merged. (thanks!)