-
Story
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
-
False
-
None
-
False
-
NetObserv - Sprint 216, NetObserv - Sprint 217, NetObserv - Sprint 218
Follow-up on: https://issues.redhat.com/browse/NETOBSERV-135 (super-columns)
Some filters are slightly modified:
- "Kubernetes Object" and "Kubernetes Owner Object" are merged into a single filter which is simply named "Resource".
- "Owner Kind" is merged into "Kind". The rationale is that Pod, Service and Node kinds are always of type "Kind", whereas others such as Deployment or DaemonSets are always for Owner Kinds (the same logic is used to for the Resource filter mentioned above, as it can target both owner and non-owner fields).
- We briefly discussed about renaming "Owner" to "Workload". I'm still not 100% sure what's the best wording to have for that. Strictly speaking, this should be "Owner controller", but that's a bit long, and maybe not a well known notion for users.
- I'm also renaming "Host" to "Node IP", as Host can be more ambiguous unlike Node.
Cf feedback in https://github.com/netobserv/network-observability-console-plugin/pull/92#issuecomment-1067730317
And https://docs.google.com/document/d/1eXROSe-ZB17FbjUGrCEOfEvQQGI6LTMcAYuh1EINuTU/edit#
- relates to
-
NETOBSERV-135 UI: super-columns source/destination
- Closed
- links to