Sebastian Florek
Sebastian Florek
We could do that, but it's not really critical or very useful for users. I'd say that this has a very low priority.
How does it break its naming design?
hmm... that's fine. If you are willing to create PR to support that I am fine with it.
I am not sure, I fully understand. Do you want to see a message why pod was killed/stopped or do you want to access some log file that was stored...
Is there a way to do that using `kubectl` other than diving into the container with `kubectl exec`? I am asking because we want to rely mostly on the API....
Ok, this should be easy to replicate then.
/lifecycle frozen
This might be because at the moment we do not support powershell :) Only basic unix shells.
We were planning to add autocomplete and some support for docker, and possibly other providers but there were many other things to do and polish before release. I believe this...
Test that on latest v2 beta. v1 is not supported anymore.