-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Open controller shortcut #1747
Comments
Agreed this could be a nifty feature. Should be relatively simple to determine - look up the resource's owner references and iterate to find an entry with
@sralloza you mention pods but I don't see a reason to limit the feature to a particular resource. It would be useful to navigate "upward" from any resource, such as Pod -> ReplicaSet, EndpointSlice -> Service, or PVC -> PV. I'm not familiar enough with the codebase to say how this would be implemented, but I can dig a little to gauge complexity. |
Believe this is definitely doable. As predicted finding the controller resource is straightforward. The tricky part then seems to be changing the view to display the resource. In cases like hitting |
I gave it a shot with #2133, let me know what you think. |
I was just looking for this feature! Also completley new to k9s, but would it be possible to jump to any kind of resource? I often find myself going to the owning custom resource, like cert-manager certificates/challenges/orders etc, or CloudNative-PGs PostgresCluster (owns the pod) etc... |
See my comment in the PR. I didn't find an easy way on first try. But it should be possible. |
In case anyone else lands here and can't find the shortcut: Also, this shortcut is only available in the resource list view, not the resource's |
In the pods view I usually want to open the controller of a specific pod (ReplicaSet -> Deployment, for example) and then restart the deployment, without navigating to the deployments view, filter them out and selecting the one I need.
It would be awesome if k9s supported this with a shortcut.
The text was updated successfully, but these errors were encountered: