API for remote command execution

[hongchaodeng]

In shell, you can use:

• kubectl port-forward to send requests to a pod's endpoint
• kubectl exec to execute commands in a pod

However, these are not obvious, easy to achieve in client API.
It would be great to provide easy to use API for such functionality.

[tamalsaha]

I was also looking for this. It seems to me that this support has been added only very recently https://github.com/kubernetes/client-go/tree/master/tools/remotecommand

[TimBozeman]

Do you know how to use remotecommand?

I tried to cannibalize this implementation
https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/blob/6a00fe8b7999a2b6bb34698c30db93665def55ff/executors/kubernetes/exec.go
, but can't seem to get it going. I keep getting a "Timeout occured".

[wefine]

Hi, @TimBozeman

Do you know how to use remotecommand now?

[tamalsaha]

@wefine , here are some example using client-go 5.x (master)

port-forward:
https://github.com/appscode/swift/blob/27d961dc386eef482127338d8000b3439085fb50/pkg/factory/tunnel.go#L41

exec:
https://github.com/appscode/searchlight/blob/22632646424bdd34c98bdaec87553fd182a85945/plugins/check_pod_exec/lib.go#L62

[TimBozeman]

That's pretty much what I'm doing. Another example
https://github.com/zalando-incubator/postgres-operator/blob/master/pkg/cluster/exec.go

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

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]

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

[davecramer]

the command will timeout if there is no response to stdout or stderr

[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

[slinkydeveloper]

👍 I think we need an API to simplify access to this functionality, I wish to contribute. Someone can point me where I can start? 😄