A few users (e.g. 1) have been confused about why they cannot delete clusters from Headlamp when in fact that's possible but we've restricted it to only clusters added from Headlamp itself. The reasons for this were that we didn't want to eventually let the user delete a cluster from their kubeconfig when thinking they're deleting it just from Headlamp. However, the reason why they cannot delete such clusters is not clear to users and not even practical according to some.

The way to fix this, IMO, is to allow users to delete any clusters, but making what they are doing very clear to them.
This would be:

• Show the origin of each cluster in the home view #1632
• When deleting a cluster from Headlamp, we have a confirmation dialog that informs the user about where the cluster came from. And in the case of it coming from non-Headlamp origin (like the kubeconfig), we should reinforce that it will delete it from there too.

Alternatively, we could ask the user whether they want to delete non-Headlamp-origin clusters just from Headlamp (i.e. hide them), or also from their config file.