Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Done
-
1.3.0
Description
With the default executor, health and readiness checks are run in their own nested containers, whose sandboxes are cleaned up right before performing the next check. This makes access to stdout/stderr of previous runs of the check command effectively impossible.
Although the exit code of the command being run is reported in a task status, it is often necessary to see the command's actual output when debugging a framework issue, so the ability to access this output via the executor logs would be helpful.