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

show k8s application namespaces only #1423

Closed
rade opened this issue May 3, 2016 · 2 comments
Closed

show k8s application namespaces only #1423

rade opened this issue May 3, 2016 · 2 comments
Labels
component/ui Predominantly a front-end issue; most/all of the work can be completed by a f/e developer feature Indicates that issue is related to new end user functionality k8s Pertains to integration with Kubernetes needs-design UI representation/flow requires a fair amount of thought
Milestone

Comments

@rade
Copy link
Member

rade commented May 3, 2016

ATM it is possible to filter by individual namespace, or show all namespaces. This leaves out one important use-case, I reckon: showing all except the system namespace. i.e. the selector should work similar to the existing selector for containers... 'system | application | both'.

Related to #1421 though note that selecting all but the system namespace would be an incredible tedious way to go about the above.

@tomwilkie tomwilkie added the k8s Pertains to integration with Kubernetes label May 3, 2016
@rade rade added the feature Indicates that issue is related to new end user functionality label Jul 4, 2016
@2opremio
Copy link
Contributor

2opremio commented Sep 8, 2016

I see a general solution for this. We could do something similar to Mute and and Solo in mixing desks: http://mixere.sourceforge.net/Help/Tracks/Mute-Solo.htm

@rade rade added the component/ui Predominantly a front-end issue; most/all of the work can be completed by a f/e developer label Nov 17, 2016
@rade rade modified the milestone: Backlog Jan 11, 2017
@rade rade added the needs-design UI representation/flow requires a fair amount of thought label Jan 11, 2017
@pidster pidster modified the milestones: Backlog, Next Feb 14, 2017
@2opremio 2opremio modified the milestones: Next, 1.3 Feb 16, 2017
@rade rade modified the milestones: 1.3, Next, Backlog Jul 12, 2017
@2opremio
Copy link
Contributor

@rade I think we support this usecase now. Closing, please re-open if you don't agree.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/ui Predominantly a front-end issue; most/all of the work can be completed by a f/e developer feature Indicates that issue is related to new end user functionality k8s Pertains to integration with Kubernetes needs-design UI representation/flow requires a fair amount of thought
Projects
None yet
Development

No branches or pull requests

4 participants