No Workload Error surfacing #50
Description
What task were you trying to complete?
Deploying a Workload
Describe the usability issue
If a workload I've deployed has an error, I have no way to see the container logs to be able to know the error occurred or figure out how to debug it.
Why was this confusing or difficult for you?
I have to guess what went wrong and try multiple deployments until I fix it.
What did you expect to happen instead? (Optional)
I'd like to have logs surfaced in some way. Also the workload operator itself could have an error and that also isn't surfaced to the user, they'll have no way of knowing what's wrong.
Do you have any suggestions for improvement? (Optional)
Surface all errors back up the stack as much as possible, through various status fields or logging services.
Relevant URL or Section of the Application (Optional)
No response
Attachments / Screenshots (Optional)
No response