You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my k9s config folder, I have a views.yml file to change the default sort order of the events view:
k9s:
views:
v1/events:
sortColumn: LAST SEEN:aschelm.toolkit.fluxcd.io/v2beta1/helmreleases:
sortColumn: NAMESPACE:desc
In 0.27.3 or less, the view is correctly rendered, sorting events from most recent, to least recent. But when updating to 0.27.4, the custom sort order is ignored. And the default order, LAST SEEN:desc is used:
To Reproduce
Steps to reproduce the behavior:
Create a views.yml file which changes the sort order of v1/events
Use version 0.27.3, and note that the sort order is correct
Upgrade to 0.27.4 and note that the sort order is ignored
Expected behavior
k9s should use the sort order requested in views.yml
Screenshots
See above
Versions (please complete the following information):
OS: Windows and Linux
K9s: 0.27.4
K8s: Many. But 1.24.14 in the screenshots
Additional context
I looked at the list of commits between 0.27.3 and 0.27.4, and nothing immediately sprung up as a culprit. The only commit that seemed semi-related was this: ab9f960
But I'm not familiar enough with the code to know if that's actually related.
The text was updated successfully, but these errors were encountered:
Describe the bug
In my k9s config folder, I have a views.yml file to change the default sort order of the
events
view:In 0.27.3 or less, the view is correctly rendered, sorting events from most recent, to least recent. But when updating to 0.27.4, the custom sort order is ignored. And the default order,
LAST SEEN:desc
is used:To Reproduce
Steps to reproduce the behavior:
v1/events
Expected behavior
k9s should use the sort order requested in views.yml
Screenshots
See above
Versions (please complete the following information):
Additional context
I looked at the list of commits between 0.27.3 and 0.27.4, and nothing immediately sprung up as a culprit. The only commit that seemed semi-related was this: ab9f960
But I'm not familiar enough with the code to know if that's actually related.
The text was updated successfully, but these errors were encountered: