Allow interactive command sessions in `deis run`

[jeroenvisser101]

(from deis/deis#117 (comment))

This seems to be a longstanding issue but something that would be super nice for Workflow.

Is this planned yet for v2? I couldn't find any issues referencing it.

[bacongobbler]

Hey @jeroenvisser101, this is not yet slated as something for v2, however now that we are using k8s this should be relatively easier to implement compared to v1.

[jeroenvisser101]

@bacongobbler would proxying this locally to kubectl be an option? That would make this very simple to implement, I think. (it would create a new runner pod, get the pod name, and then exec -ti in that pod, delete when done?)

[bacongobbler]

I don't think we can assume that the kubernetes api server is publicly accessible, which strikes out the idea of proxying to kubectl.

[bacongobbler]

The run implementation currently works like that (create a runner pod, get the pod name, wait for it to finish, retrieve the logs, delete when done), however the limitations are still the same as deis/deis#117. The limitation being that WSGI cannot handle long-running request/responses such as a websocket. We need to effectively create a new component to handle the proxying between the pod and the client outside of the controller w/auth... same for deis logs -f for deis/deis#465.

[rimusz]

any update on this?

[Cryptophobia]

This issue was moved to teamhephy/workflow-cli#28