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
Describe the bug
When using ^ and $ regex anchors, the filtering no longer works and returns an empty list instead of actually matching on resource names.
To Reproduce
Steps to reproduce the behavior:
Go to a resource list
Click on / to start filtering
Enter a regex filter like ^fancyPants
Expect to see resources with names that start with fancyPants, but actually nothing shows up.
Enter a regex filter like fancyPants
Resources with that substring in their name show up, including ones that start with it
Historical Documents
N/A
Expected behavior
Resources matching the regex should show up since the k9s docs say:
Regex2 supported
Screenshots
N/A
Versions (please complete the following information):
OS: OSX Sonoma 14.x.x
K9s: 0.32.5
K8s: 1.3x.x
Additional context
N/A
The text was updated successfully, but these errors were encountered:
Resource filtering in k9s is very generic. User may want to filter on name but also ips, nodes, etc... for a given resource.
The way search currently works is by flattening out rows and grepping on that.
RX anchors tho supported are not effective here given the current strategy.
Describe the bug
When using
^
and$
regex anchors, the filtering no longer works and returns an empty list instead of actually matching on resource names.To Reproduce
Steps to reproduce the behavior:
/
to start filtering^fancyPants
fancyPants
, but actually nothing shows up.fancyPants
Historical Documents
N/A
Expected behavior
Resources matching the regex should show up since the
k9s
docs say:Screenshots
N/A
Versions (please complete the following information):
Additional context
N/A
The text was updated successfully, but these errors were encountered: