Replies: 1 comment 1 reply
-
Not a real answer, but as you have found out in #1063, this is hard due to actual terminal behaviour is hard to deal with. We just expose the raw streams, whereas kubectl invokes a terminal handling library (moby/term) for its stream handling. And we are more a trying to match behaviour of client-go than kubectl (kubectl-like behaviour is just for showcasing in the examples). We currently do not have a good way to show how to do this, so if anyone have more full examples that they can link to / would like to extend our examples / or have some way of plugging crossterm into the stdout stream, it would be very cool to see! This PR is the first thing we have that is using |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I am checking the examples provided and can't figure out how to hook the stdin in my laptop to the one in the container. Basically I want to be able to reproduce the same functionality as
kubectl exec -it <pod name> -c <container name> -- sh
.This is what I tried so far:
I am not sure I am doing it properly because the stdout seems out of sync meaning I need to press enter twice for each command to see the output.
As an example
I guess I am doing it wrong...
Any hint on how to get the interactive session done properly?
Beta Was this translation helpful? Give feedback.
All reactions