Client-go: Support for Exec & Attach APIs

Created on 22 Nov 2016 · 13Comments · Source: kubernetes/client-go

Currently the client doesn't seem to support the Exec into container, attach to container APIs. The client should support those APIs.

help wanted lifecyclrotten

Source

ianlewis

👍17

Most helpful comment

Until the work on this ticket is done, it is pretty simple to use ther rest.Config to create your own exec call. I created a simple example. A detailed description is also available.

rmohr on 15 May 2017

😄1 👍1

All 13 comments

Yes its will be great to support exec and attach to container from the client-go.
I really need it.

JrCs on 16 Dec 2016

I agree, we should support these.

lavalamp on 3 Jan 2017

Until the work on this ticket is done, it is pretty simple to use ther rest.Config to create your own exec call. I created a simple example. A detailed description is also available.

rmohr on 15 May 2017

😄1 👍1

@rmohr thanks for the simple example.
The only problem with your example is that you can't detect if the command return with a non zero exit code.

JrCs on 22 May 2017

I need this enough to pick it up and work on a PR.

Seems like kubectl would also benefit from this

Going to make an effort at adding client support for an Exec() method (not sure where it should live) which allows different Executors, and has a default one like this.

Thoughts? Suggestions? Cryptic warnings?

topherbullock on 18 Jul 2017

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.

Prevent issues from auto-closing with an /lifecycle frozen comment.

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 on 1 Jan 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
/remove-lifecycle stale

fejta-bot on 31 Jan 2018

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

fejta-bot on 2 Mar 2018

What's the update on this?

geekodour on 3 Apr 2019

So should we reopen this issue?

LeoLiuYan on 28 Aug 2019

I'll be happy to work on this, If provided some initial pointers. The current way to do this seems to be using websockets only. right?

geekodour on 28 Aug 2019

/reopen

LeoLiuYan on 28 Aug 2019

@LeoLiuYan: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to this:

/reopen

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.