Running an interactive bash terminal

[ace-subido]

Proposing to add a command that would conveniently create a bash session to a running container:

kcu run console staging/web

[ramontayag]

I guess it's safe to assume that all of them will have bash right? I don't know if it's something you can gut out completely.

[ace-subido]

Maybe we could say, interactive? Then supply a shell type?

• kcu interactive bash staging/web
• kcu interactive shell staging/web

I was thinking under the hood it runs this:

kubectl exec -it #{pod_name} -n #{namespace} -- /bin/#{shell_type}

[ramontayag]

What happens if there are multiple pods? I guess ideally, it would behave like heroku: it'll spin up a new pod (perhaps copy the config from the deployment, but launch a Kubernetes job? Don't know yet...), and log you into that. This way, if there are 5 devs that request a console, they won't be overloading a machine.

This, however, sounds like a bunch of work.

I'm not opposed to having an interim command that picks a pod at random.

[ace-subido]

Hmm, yeah, spinning up a pod is the better path. It should launch a container based on the deployment with ["/bin/bash"] as the command. We can do this via:

kubectl run --image=<image_name> --namespace <namespace> --command -- #{shell_type}
kubectl exec -it <pod_name> --namespace <namespace> -- /bin/#{shell_type>

Maybe fire a delete resource once exited to delete cloned container?