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

Feature Request: kubectl describe pod #20

Open
sabrehagen opened this issue Oct 4, 2018 · 1 comment
Open

Feature Request: kubectl describe pod #20

sabrehagen opened this issue Oct 4, 2018 · 1 comment
Labels
Projects

Comments

@sabrehagen
Copy link

sabrehagen commented Oct 4, 2018

Thanks for an incredibly useful utility. Kubebox is now part of my daily development toolkit.

One of the most useful commands is kubectl describe pod. This command answers questions such as:

  • What image is this pod running?
  • How many restarts has the pod had?
  • What are the pod's environment variables?
  • What volumes are mounted to the pod?
  • What events have occurred in the pod's history?

All these questions are answered with one kubectl describe pod, and are critical to investigating the state of a kubernetes environment.

In my opinion, adding a Pod or Info tab to the Resources pane would be the appropriate place to display this information. This is because kubectl describe pod output is metadata about the pod, just as Memory, CPU, and Network activity are metadata about the pod.

Currently this is the only task I need to step outside of Kubebox for. If Kubebox supported this natively all my kubernetes interactions would be supported from within the app.

Thanks!

@astefanutti
Copy link
Owner

Thanks for the feedback! I totally agree with you.

The next big step for Kubebox is refactoring the UI to support other kinds of primitives (like services, deployments, ...), improve navigation across them and access further details, like those output by the kubectl describe pod command.

The idea of adding a tab to the Resources panel is interesting. I think it'd be a quick win before having that UI refactoring ready. Even if the resources are actually related to the selected container within the pod, I think it'd be acceptable to have that describe pod tab.

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

No branches or pull requests

2 participants