derailed
Filter out/Ingore a namespace
Looking to filter out a namespace like kube-system with the assumption being all my applications will be outside of that namespace. I typically am either working on kube-system or everything else.
Could be as simple as :pod !kube-system.
Perhaps it's possible and I missed it.
A similar nice feature would be to be able to have a view on ressources across multiple namespaces for example: :pod monitoring,default,auth
+1, I want this, yes! I want to create a custom view which lists all deployment in all namespaces starting with "NAMESPACENAME-", so i can easily check them and restart when needed...
This issue is stale because it has been open for 30 days with no activity.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
This issue is stale because it has been open for 30 days with no activity.
Didn't the big issue trackers implement follow support to avoid mass posting +1, but somehow "stale bots" make sense to punish that lack of spam? Does writing a bot to say nonsense 1 day shy of the stale bot interval make this issue "not stale"? Did someone taste an issue once to figure out they go stale? When issues are closed does that mean someone ate them?
Close it if not a good idea or not acceptable to project, otherwise leave it alone until fixed.
This issue is stale because it has been open for 30 days with no activity.