-
Story
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
Quality / Stability / Reliability
-
False
-
-
False
-
None
-
None
-
None
-
None
-
None
Description of Problem
user is hard to find out the container ready status in Containers table, it only has State
How reproducible
(Always)
Steps to Reproduce
- Deploy some pod with more than one container and at least one can not be ready.
In my case, I installed "OpenShift LightSpeed Operator" and created OLSConfig but something wrong in OLSConfig so that "lightspeed-service-api" container can not be in Ready status
$ oc get pod lightspeed-app-server-5b8d547988-w45lx NAME READY STATUS RESTARTS AGE lightspeed-app-server-5b8d547988-w45lx 1/2 Running 0 35m $ oc get pod lightspeed-app-server-5b8d547988-w45lx -o json | jq '.status.containerStatuses[] | .name,.state,.ready' "lightspeed-service-api" { "running": { "startedAt": "2025-10-09T07:06:19Z" } } false "lightspeed-service-user-data-collector" { "running": { "startedAt": "2025-10-09T07:06:21Z" } } true
- View Pod details via Workloads -> Pods -> click on pod lightspeed-app-server-xxxxx-xxxx -> Check 'Containers' table
Actual Behavior
In 'Containers' table, we see both containers has State: Running so we have no idea which container is not ready.
If we scroll down to 'Conditions' table at the bottom we can see the detailed message describing which container is not ready
Expected Behavior
It would be great if we can add a Ready column in Containers table so that container readiness status will be more noticeable to user