You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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):
kubectl exec -ti to an offloaded pod
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 !
The text was updated successfully, but these errors were encountered:
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" podHow to reproduce it (as minimally and precisely as possible):
kubectl exec -ti
to an offloaded podvim
to open a medium/large fileAnything else we need to know?:
Environment:
kubectl version
): 1.26 on local, 1.29 on remoteThanks !
The text was updated successfully, but these errors were encountered: