irrelevant views clutter the UI

[rade]

If I am not running k8s, I have no use for the 'Pods' view, or any other k8s views we are contemplating. They just become a distraction and might even confuse users who know nothing about k8s.

The same applies to any other platform-specific views we might add.

Suggestion: we should be able to detect fairly accurately whether we have any k8s/etc in a report, and limit the views we show accordingly.

[paulbellamy]

The kubernetes view are only shown if k8s is detected by the probe.

[rade]

The kubernetes view are only shown if k8s is detected by the probe.

Since when? I always see 'Pods - By Service', even in the current master, and I sure am not running k8s.

[tomwilkie]

What version are you running @rade?

We did a bunch of work to make what paul said the case, we might have missed something.

Please include a report.

[paulbellamy]

[tomwilkie]

Hmpf. Thats post 0.14 at least.

[rade]

Hmpf. Thats post 0.14 at least.

I said I was running current master!

[tomwilkie]

@paulbellamy I think I might propagate a kubernetes flag in the report in kubernetes is enabled, and filter all nodes from the view if this flag is not set. Thoughts?

[paulbellamy]

I'm a bit puzzled why FilterEmpty(report.Pod, ...) Isn't removing the managed node, maybe we need to do a FilterUnconnectedPseudo on it?

[tomwilkie]

I'm a bit puzzled why FilterEmpty(report.Pod, ...) Isn't removing the managed node, maybe we need to do a FilterUnconnectedPseudo on it?

The unmanaged nodes is connected to itself in this instance, so therefore is not unconnected.

But in general it could be pointing to the internet (or the internet pointing at it) so I don't think its enough to rely on hiding the view if there are no nodes - hence the idea to propagate the flag.