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

The "Kubectl shell" icon is always disabled #8151

Open
jandubois opened this issue Jan 27, 2025 · 2 comments
Open

The "Kubectl shell" icon is always disabled #8151

jandubois opened this issue Jan 27, 2025 · 2 comments
Assignees

Comments

@jandubois
Copy link
Member

I've gone to the "Pods" page, selected a pod, but I could not figure out how to open a shell window:

Image

@rak-phillip
Copy link
Contributor

It appears that the minimal backend that we run with Steve might not support invoking the shell out of the box - this is the behavior that Rancher Desktop has today. We have two options for addressing this:

  1. There's an extension hook, hideKubeShell, that we can utilize so that the icon is not present at all
  2. Investigate what might be missing to see if we can implement the shell feature in Rancher Desktop

@jandubois
Copy link
Member Author

jandubois commented Feb 6, 2025

Looks like I was confused: I assumed that the button would provide shell access to a pod, but it actually provides a shell to run kubectl against the cluster. This is not useful in Rancher Desktop where the user can simply use a local terminal window.

Creating a shell inside a Pod is available via the Pod context menu and is working fine.

So just hiding the toolbar button (together with the copy/download kubeconfig buttons) is sufficient.

For reference, the functionality of the kubectl shell button is documented at https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/manage-clusters/access-clusters/use-kubectl-and-kubeconfig.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants