TUI shows "Ready" even though the process has aborted

[teto]

I have my redis service who failed to start because I had already a running instance on my machine.
The readiness probe is configured with

    readiness_probe:
      exec:
        command:
          redis-cli ping

and I found it weird that it showed me the service as "Ready" even though the process failed

I think it does because the probe actually succeeds but it's weird to mark the process "Ready" and at the same time "Completed".

In terms of UX, I think we can do better than showing "Completed" when the exit status != 0 to convey the idea of an error though I am not sure what.
"Failed" is ambiguous, aka it doesn't say if the process ever started.
Completed with error might be long.

I wonder if it's worth to have a column per exit code. I suppose it's done to sort them out ? One way could be to show the exit code next to the "Completed" otherwise, e.g., Completed (1)