Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Initial terminal dimensions for kubectl exec are not set correctly for offloaded pods #2448

Open
EladDolev opened this issue Apr 10, 2024 · 0 comments
Labels
kind/bug Something isn't working

Comments

@EladDolev
Copy link
Contributor

What happened:

issue is very much the same as in this bug

it seems that are multiple such bugs opened throughout the years on multiple OSS projects, k8s included
seems that the root cause is that a mechanism that is responsible for passing some arguments for the shell when execing to a container (it is not restricted to k8s) is not working properly

What you expected to happen:

kubectl exec to an offloaded pod should work the same as to a "regular" pod

How to reproduce it (as minimally and precisely as possible):

  1. kubectl exec -ti to an offloaded pod
  2. write 80 chars or less in the terminal OR use the arrow keys OR use vim to open a medium/large file

Anything else we need to know?:

Environment:

  • Liqo version: v0.10.1
  • Kubernetes version (use kubectl version): 1.26 on local, 1.29 on remote
  • Cloud provider or hardware configuration: GKE. local running data plane v1 remote running data plane v2 (Cillium)

Thanks !

@EladDolev EladDolev added the kind/bug Something isn't working label Apr 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant