Is your feature request related to a problem? Please describe.
When the node resources become low, the Pod may be evicted many times. For example:
The status can be "Error", "Completed", "ContainerStatusUnknown", "Init:1/1"... But if check get po -o yaml, the status.reason are all Evicted (except the "Completed").
message: 'The node was low on resource: memory. Threshold quantity: 100Mi, available:
35365Ki. '
phase: Failed
qosClass: Burstable
reason: Evicted
startTime: "2024-10-05T01:37:24Z"
(For the "Completed" one, there is no reason but the message is same.)
At the time, Status cannot loyally reflect why the Pod stuck here. So status.reason can be important.
Describe the solution you'd like
Add status.reason into Azure portal. Allow user to customize what can be put as a column will be better.
Please also consider adding this into "Deployment" page:
Is your feature request related to a problem? Please describe. When the node resources become low, the Pod may be evicted many times. For example:
The status can be "Error", "Completed", "ContainerStatusUnknown", "Init:1/1"... But if check
get po -o yaml
, thestatus.reason
are allEvicted
(except the "Completed").(For the "Completed" one, there is no reason but the message is same.)
At the time, Status cannot loyally reflect why the Pod stuck here. So
status.reason
can be important.Describe the solution you'd like Add
status.reason
into Azure portal. Allow user to customize what can be put as a column will be better.Please also consider adding this into "Deployment" page: