Sebastian Florek

Like @maciaszczykm mentioned, I'd also add a new endpoint like `api/v1/nodes/metrics` that would return cluster-wide metrics.

My original concerns still exist. I'd prefer to have a separate `controlled by` card that would be added on a per resource basis since there are resources that do not...

Since https://github.com/kubernetes/dashboard/pull/7047 has been merged and it introduces major architecture changes we should close this PR. If you are willing to work on it, you can open a new PR...

We are already displaying [external endpoints](https://github.com/kubernetes/dashboard/blob/master/src/app/frontend/service/detail/info.html#L43) of the service as links but to be honest I haven't actually seen it in action. I guess it only works with correctly configured...

/reopen /lifecycle frozen

If you want to deploy Dashboard in a different namespace you should: 1. Download yaml file and change `kubernetes-dashboard` namespace to the one of your choice 2. Update [--namespace](https://github.com/kubernetes/dashboard/blob/master/aio/deploy/recommended.yaml#L200) argument...

I don't think so. We have updated the logic quite a long time ago to use namespace from the dashboard binary `--namespace` argument. All our dashboard exclusive resources are using...

The lack of create secrets permissions for Dashboard is intentional and we don't want to change it. That's why secret is created via yaml and should not be deleted. We...

> Yeah I understood the point but can we make the possibility to change the secrets name? That's my main point of this topic. You might have missed this part...

I'd also add ThirdPartyResource to the list. I can start initial work on that and introduce a way to easily add new object creation pages.