We have registered a cluster-scoped CRD to the dashboard. This works fine as long as the Namespace selector in the menu on the left is set to "All Namespaces". When a namespace is selected and we navigate to the Extension, it shows an error because it tries to load all CRD instances for the selected namespaces (404 is returned by the api server in that case).
When selecting a cluster-scoped extension, it should load and display all instances on the cluster level (similar to how ClusterTasks is implemented)
Thanks, Fabian
Thanks for reporting, I'm taking a look at this now and have a partial fix. I'm testing the remaining changes now and should have a PR ready later today / tomorrow.
/assign
This is included in the Dashboard 0.10.0 release
Thanks for taking care of this so quickly 馃憤