Kubectl cp error using kubectl version 1.14.2

[richardmatthewsdev]

Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see http://kubernetes.io/docs/troubleshooting/.):

What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.):

error: open is a directory

---

Is this a BUG REPORT or FEATURE REQUEST? (choose one):

Kubernetes version (use kubectl version):

kubernetes 1.11.7

Environment:

• Cloud provider or hardware configuration: AWS
• OS (e.g. from /etc/os-release): ubuntu
• Kernel (e.g. uname -a):
• Install tools: kops
• Others:

What happened:

kubectl cp from a pod to a destionation directory on your machine does not copy the file and results in this error error: open <destination> is a directory

What you expected to happen:

The file is copied from the pod to my machine.

How to reproduce it (as minimally and precisely as possible):

install kubectl version 1.14.2 and attempt to copy a file from a pod to your local machine.

Anything else we need to know:

kubectl cp command works correctly on 1.14.1.

[pswica]

I tested and had this issue as well. I tried to address in my PR here: kubernetes/kubernetes#78785

[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

[seans3]

/remove-lifecycle stale

[danton721]

Any solution? Having the same issue over here

[LeszekChojnacki]

Any solution? Having the same issue over here

[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

[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.