What would you like to be added:
Have a page with a list of seeds as we have for the shoots. Maybe this list should only be visible to operators (even if users can read seed resources)
We already have the seeds in the dashboard, however we would need to watch them to make the seed status reactive.
Maybe it also makes sense to read the ManagedSeed resources to identify the associated shoot. Right now this is done via a name assumption which might not always work depending on the landscape setup.
If we have this information in the dashboard, the link to seed will also work from the cluster list.
The link will lead to the seed resource, but we should also offer a way to switch to shoot (if available) and back. Also add information that a shoot belongs to a managed seed to the shoot details page.
Why is this needed:
Get additional information about seeds, including their status
Some seeds are not managed, so they can not be accessed via their shoot resource
We could also show the operator.gardener.cloud/v1alpha1.Garden resource. It is similar like a Seed/Shoot and has conditions that would be interesting for human operators.
What would you like to be added: Have a page with a list of seeds as we have for the shoots. Maybe this list should only be visible to operators (even if users can read seed resources) We already have the seeds in the dashboard, however we would need to watch them to make the seed status reactive. Maybe it also makes sense to read the ManagedSeed resources to identify the associated shoot. Right now this is done via a name assumption which might not always work depending on the landscape setup. If we have this information in the dashboard, the link to seed will also work from the cluster list. The link will lead to the seed resource, but we should also offer a way to switch to shoot (if available) and back. Also add information that a shoot belongs to a managed seed to the shoot details page.
See also
Why is this needed: Get additional information about seeds, including their status Some seeds are not managed, so they can not be accessed via their shoot resource