Question: FieldSelector != is not supported by FakeClient

[marvinbstackit]

I am currently writing unit tests in my go application and I list events. These events can be filtered with field selectors to exclude some events. In the code everything is fine, but in the fake client the field slector will be evaluated to only support '=' and '=='. Why is this so and what does it need to support also '!='?

This is the code piece, but in the actual client is never called because the parameter is used in the api call here.

[alvaroaleman]

This predates my involvement in the project, but I believe the reason is that in most cases, ppl read from the cache and not from the api. The cache allows to set up indexes and these are used through fieldSelectors. The problem now is that there is no good way to find all elements that are not in a given index, which is why both the cache reader and the fake client error out when trying to use such a fieldSelector.