Closed freegroup closed 2 years ago
I'm not sure about this but I think we had a similar request in the past but I cannot remember the outcome. Anyway, this is not a dashboard issue. Please open a issue in g/g repository and ask if they find a way to transport the issue to the shoot status resource. If not, we cannot display the issue in the dashboard
Just to make it clear: Of course there are ways to access this information. However, right now we depend on the information we get from the shoot / shoot status resource. If we want to display other information this would require a lot of work. I'm not saying that we do not want to display this information, we even have a issue for this: https://github.com/gardener/dashboard/issues/26 It is just not feasible with the current implementation. That's why I closed the issue for now. maybe gardener can improve here but as I already stated I think they have similar issues as the error happens during creation and they cannot put the error into the status resource at this point in time if I remember correctly.
During the (broken) creation of a gardener cluster an error happens in the gardener backend. Unfortunately this error is not visible in the dashboard. We can only see a spinning icon and a
pending
state message.Support team inspect this error and we get this information back
I think it is much better to transport this error to the enduser instead bothering the support team. :-)
Example of wrong YAML