Peter Sutter

Having a place in the dashboard to notify users about landscape specific issues is still open. This is somewhat related to https://github.com/gardener/dashboard/issues/583.

Hi @berendt, have you checked if https://github.com/gardener/dashboard/blob/master/docs/usage/custom-fields.md fits your needs?

@berendt yes currently you can only change the custom fields via the API, but this can also be done by the project owners, so you do not have to dictate...

done :)

> This is not strictly a Dashboard topic, rather a generic one, but it would be made visible explicitly there true, we can certainly display when it was last updated,...

@uvwild The kubeconfig that you use for the garden config must be the (virtual) garden cluster. It's the cluster that exposed the `Project`, `Shoot`, `Seed` etc. resources

see also https://banzaicloud.com/blog/kubeconfig-security/

If the user confirms that the kubeconfig is safe you could create a hash of the kubeconfig and update the garden config. As long as the hash stays the same...

`kubeswitch` depends on having all the required kubeconfigs locally / fetch them in advance. With OIDC kubeconfigs this "may" not be that much of an issue, however I would rather...

sounds good