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

Filter by kubernetes namespace in CONTAINERS view #1504

Closed
janwillies opened this issue May 13, 2016 · 4 comments · Fixed by #2362
Closed

Filter by kubernetes namespace in CONTAINERS view #1504

janwillies opened this issue May 13, 2016 · 4 comments · Fixed by #2362
Assignees
Labels
chore Related to fix/refinement/improvement of end user or new/existing developer functionality k8s Pertains to integration with Kubernetes

Comments

@janwillies
Copy link

With scope-0.15 it's possible to filter by namespace in the PODS view which is great when having lots of namespaces. From there however it's difficult to get to the right container as all containers are listed in the sidebar, not just the ones belonging to the filtered namespace:

scope-ns-issue

A namespace filter in the CONTAINERS view would allow to directly jump into the container and e.g. open a shell.

@2opremio suggested making the namespace filter global

@tomwilkie tomwilkie added the k8s Pertains to integration with Kubernetes label May 16, 2016
@rade rade added the chore Related to fix/refinement/improvement of end user or new/existing developer functionality label Jul 4, 2016
@rade
Copy link
Member

rade commented Aug 26, 2016

The issue with k8s view detail panels showing pods/containers/processes belonging to a different namespace was actually a bug - see #1824 - and got fixed in #1832.

@pidster pidster added this to the Next milestone Feb 14, 2017
@ekimekim ekimekim self-assigned this Feb 22, 2017
@ekimekim
Copy link
Contributor

Should the container by image and container by dns topologies also have this filter?

@rade
Copy link
Member

rade commented Feb 28, 2017

Yes.

@rade
Copy link
Member

rade commented Mar 17, 2017

PR #2285 got reverted in #2348, so re-opening this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore Related to fix/refinement/improvement of end user or new/existing developer functionality k8s Pertains to integration with Kubernetes
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants