Created attachment 1872651 [details] local-cluster resource shown in All Clusters perspective Description of problem: When using the All Clusters perspective that is provided when RHACM console plugins are enabled, if a user visits a resource page, there is no indication that it defaults to local-cluster. Version-Release number of selected component (if applicable): 4.10.6 How reproducible: Always Steps to Reproduce: 1. Install RHACM 2.5 on OCP 4.10.6 2. Switch to All Clusters persepective 3. Change route to /k8s/cluster/config.openshift.io~v1~Infrastructure/cluster/yaml (for example) in the browser location bar Actual results: Perspective remains as All Clusters, so there is no indication which cluster this resource belongs to. Expected results: Additional info:
Hey Kevin, thanks for reporting this issue. To me it looks more like an RFE then a bug, since we should be showing the cluster ownership, for all the resources, when in "All Clusters" perspective. I would suggest to create a story in https://issues.redhat.com/browse/CONSOLE-3052 epic. Thoughts?
I believe @spadgett suggested I open a bug for this. The problem is that when you load a console page, the last used perspective is active. This was fine when dealing with a single cluster, but when you view a page from the OCP console but your last perspective was "All Clusters" then there is nothing to indicate to the user that you are viewing a resource on "local-cluster" by default, rather than from one of your other clusters.
This is something we likely need to fix before we GA multi-cluster. It's a usability issue where you could potentially edit or delete the resource on the wrong cluster without realizing it, which could be serious if you confused stage and prod clusters for instance. I'd argue we need to treat it as a bug. The underlying problem is that we remember your last perspective. So if someone sends you a resource link and your last perspective was "All Clusters," it won't show the cluster context. Either we need to automatically switch back to one of the other perspectives or we need to show the cluster context somewhere on the page.
This bug will be addressed as part of
Closing this one since we are tracking it as part of https://issues.redhat.com/browse/CONSOLE-3323