Improve error reporting on kubectl failure
Description
Conclusion
None
Activity
Show:
Fixed
Pinned fields
Click on the next to a field label to start pinning.
Details
Details
Components
Assignee

Reporter

Priority
Fix versions
Pull Request URL
Created June 23, 2021 at 2:25 PM
Updated June 23, 2021 at 3:46 PM
Resolved June 23, 2021 at 3:46 PM
When a kubectl command fails we do not consistently report any captured stderr in the exception.
e.g. there a few places that only report "Failed to replace k8s resource" as the exception, which means the underlying cause/issue is not reported (only logged).