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
Describe the bug
Connect to the Pod's shell is not working, nothing is happening!
To Reproduce
Steps to reproduce the behavior:
Connect to your cluster and select a namespace from the list.
Go to left pane "Pods"
Pick one of your pods
Click in shell option, nothing happens
Expected behavior
The Kubectl exec command should run and a terminal on the pod should be opened
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
OS: Win 10
Version 2.4.8
Log output:
[2024-07-25 14:45:28.856] [browser] [warn] This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
[2024-07-25 14:45:28.858] [browser] [error] {}
[2024-07-25 14:48:17.818] [browser] [warn] This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
[2024-07-25 14:48:17.819] [browser] [error] {}
[2024-07-25 14:48:24.303] [browser] [warn] This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
[2024-07-25 14:48:24.304] [browser] [error] {}
The text was updated successfully, but these errors were encountered:
Describe the bug
Connect to the Pod's shell is not working, nothing is happening!
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The Kubectl exec command should run and a terminal on the pod should be opened
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Log output:
The text was updated successfully, but these errors were encountered: