-
Notifications
You must be signed in to change notification settings - Fork 40k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
swap FIRSTSEEN/LASTSEEN columns in kubectl get event -w
#27549
Conversation
This is ugly, as I already mentioned. I think we should just changed the order permanently, watch or not. (More specifically, NewHumanReadablePrinter is not idempotent. If somehow it gets invoked a second time, the headers will be swapped again and thus back to the default.) |
Conditionally swapping is ugly. +1 for changing order permanently. |
Not having LASTSEEN as the first column can confuse users into thinking that events are not delivered in order. Fixes kubernetes#27060
Done. |
I wouldn't complain if this change were to get merged in 1.3. It's a common WTH item. |
lgtm, but please edit top comment to include a one line release note in block quotes. |
Done. I assumed that eliminating the block would use the subject as the release note. |
GCE e2e build/test passed for commit bf873df. |
@k8s-bot test this [submit-queue is verifying that this PR is safe to merge] |
GCE e2e build/test passed for commit bf873df. |
Automatic merge from submit-queue |
Not having LASTSEEN as the first column can confuse users into thinking
that events are not delivered in order.
Fixes #27060