-
Notifications
You must be signed in to change notification settings - Fork 66
Add "message" field to DevWorkspace status and column for kubectl get #220
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Do we have any example when INFO may be not empty for not failed state? |
Personally, I like this idea. I dislike having to dig through the logs to find out why my devworkspace failed. I'd prefer it if we had some easy way to find out why it failed for users (and even ourselves) |
In general I'd use the field to communicate info that requires user intervention, since it cannot be hidden and a normal running state is captured by
That makes sense, I'm generally bad at naming things :D |
Just chiming in here since I'm trying to do a similar thing for the registry operator - what about exposing the detailed status message as part of the Seems like that can be done with the manager's event recorder. |
Sorry, getting back to this a little late. I don't know offhand how to do this -- could we create a follow-up issue to plan this? I think it's a good idea (I never think to use |
Yeah, I think that sounds reasonable 👍 |
Is your feature request related to a problem? Please describe.
There are many valid reasons for a DevWorkspace startup to fail and we represent status this via the
Failed
value for.status.phase
. However, the only way to get insight into why a particular DevWorkspace failed to start is by inspecting the full yaml of the DevWorkspace and checking which Conditions are set.Describe the solution you'd like
We should add a field, e.g.
Message
orStatusInfo
toDevWorkspaceStatus
and include it in the output forkubectl get
. This might result in output such ascc: @davidfestal
The text was updated successfully, but these errors were encountered: