Unable to find namespaces using specific keywords

[aresler]

Describe the bug
When searching for a specific namespace using the search key "/", some words are not searched properly. For example, "pipe", "flow" etc.

To Reproduce
Steps to reproduce the behavior:

1. Have some namespaces with a name ending with pipelines or kubeflow. e.g. project-foo-pipelines or project-foo-kubeflow
2. Go to the namespaces list (type :ns)
3. Hit the search key "/" to open the search prompt
4. Type pipe or flow to try and find the namespaces from step 1
5. Observe that all namespaces are still on-screen as if the search didn't work

Expected behavior
I would expect the resource like project-foo-pipelines to be found when searching for pipe keyword. I.e. this is the only namespace that should be on screen after filtering out all the others. However, when using this particular keyword, all namespaces are still on screen.

Most of the keywords work without a problem. I found the issue only with some specific keywords, like pipe, flow or kube.

Screenshots

Versions:

• OS: OSX 15.1.1
• K9s: v0.32.7
• K8s: client v1.25.2

[derailed]

@aresler Interesting! What does your namespaces labels look like and do they contain "pipe" | "flow"?

[aresler]

@derailed Ok, first, unfortunately, I couldn't reproduce the issue on a local minikube cluster. I created a namespace with identical name and identical labels. Then I can find it successfully using keyword pipe. This makes me think the issue is not with namespaces, but something to do with cluster/context?

Unfortunately, I'm not sure that I can share all my prod labels, but the namespace I'm trying to find does have the default label like kubernetes.io/metadata.name=project-foo-pipelines.

Please note that when I type /pipe in the search, it seems the filtering is not working at all, while if I'm using some random word like santa, the filter is applied and shows an empty list, because I don't have any namespace with santa in it. It's just a specific set of words that doesn't work on my prod cluster, I have no idea what the correlation between them is, but it does seem related to my cluster or context after all.

UPD: I'm happy to provide additional info, but if nothing comes to mind, feel free to close the issue or put it to a backlog, it's not very critical.