-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Open
Description
Is your feature request related to a problem? Please describe.
The problem is in the AGE output column.
It calculates and shows Minutes starting from 2 but not 1.
So it shows seconds to 120 and then switches to minutes.
NAME↑ PF READY STATUS RESTARTS CPU MEM %CPU/R %CPU/L %MEM/R %MEM/L IP NODE AGE
test-cronjob-29495774-v2stn ● 0/1 Completed 0 0 0 n/a n/a n/a n/a 10.64.1.223 test-server 5m33s
test-cronjob-29495775-4m65d ● 0/1 Completed 0 0 0 n/a n/a n/a n/a 10.64.1.250 test-server 4m33s
test-cronjob-29495776-465n6 ● 0/1 Completed 0 0 0 n/a n/a n/a n/a 10.64.2.58 test-server 3m33s
test-cronjob-29495777-9lg8c ● 0/1 Completed 0 0 0 n/a n/a n/a n/a 10.64.2.33 test-server 2m33s
test-cronjob-29495778-flzzw ● 0/1 Completed 0 0 0 n/a n/a n/a n/a 10.64.2.28 test-server 93s
test-cronjob-29495779-czhrt ● 0/1 Completed 0 0 0 n/a n/a n/a n/a 10.64.2.23 test-server 33s
If it sucessfuly calculates minutes from the second one, and switches to next after 60 second, why it doesn't do it for the first minute?
It simply doesn't convinient when sorting by AGE, to see this 100s PODs.
Describe the solution you'd like
I'd love to see the sorted AGE column look like:
NAME↑ PF READY STATUS RESTARTS CPU MEM %CPU/R %CPU/L %MEM/R %MEM/L IP NODE AGE
test-cronjob-29495774-v2stn ● 0/1 Completed 0 0 0 n/a n/a n/a n/a 10.64.1.223 test-server 5m33s
test-cronjob-29495775-4m65d ● 0/1 Completed 0 0 0 n/a n/a n/a n/a 10.64.1.250 test-server 4m33s
test-cronjob-29495776-465n6 ● 0/1 Completed 0 0 0 n/a n/a n/a n/a 10.64.2.58 test-server 3m33s
test-cronjob-29495777-9lg8c ● 0/1 Completed 0 0 0 n/a n/a n/a n/a 10.64.2.33 test-server 2m33s
test-cronjob-29495778-flzzw ● 0/1 Completed 0 0 0 n/a n/a n/a n/a 10.64.2.28 test-server 1m33s
test-cronjob-29495779-czhrt ● 0/1 Completed 0 0 0 n/a n/a n/a n/a 10.64.2.23 test-server 33s
It is stricter and convenient to sort and search by.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels