"non-exact field matches are not supported by the cache" when using fieldSelector with not exact fields

[sarjeet2013]

I am getting the following error when trying to get list of pods with their state filetered with fieldSelector.

"error":"non-exact field matches are not supported by the cache"

Here is the sample code:

fieldSelector, err := fields.ParseSelector("spec.nodeName=" + nodeName + ",status.phase!=" + string(corev1.PodSucceeded) + ",status.phase!=" + string(corev1.PodFailed))
activePodsList := &corev1.PodList{}
listOptions := &client.ListOptions{FieldSelector: fieldSelector}
if err := r.List(context.TODO(), listOptions, activePodsList); err != nil {
  return reconcile.Result{}, err
}

This look like a current limitation and not supported. See https://github.com/kubernetes-sigs/controller-runtime/blob/master/pkg/cache/internal/cache_reader.go#L99

[DirectXMan12]

it's unclear to me how we'd support this w/o becoming fairly complicated.

/kind feature
/priority backlog

[lawrencegripper]

In case anyone else lands here from KubeBuilder and wants an workaround I was able to create a client instance without caching using the mgr in the autogen'd main.go like this:

directClient, err := client.New(mgr.GetConfig(), client.Options{Scheme: mgr.GetScheme(), Mapper: mgr.GetRESTMapper()})
if err != nil {
	panic(err)
}

[shawn-hurley]

Another option is to use the mgr.GetReader() which will allow you to hit the API server directly with a reader interface.

[vincepri]

/kind design
/priority awaiting-more-evidence

[maplain]

figured out another approach:

1. use client.MatchingFields;
2. customize the IndexField to make it return a value that is parameterized by multiple fields

eg:

m := client.MatchingFields{
  key: getValue(obj)
}

mgr.GetFieldIndexer().IndexField(obj, key, func(xx) []string{
   return []string{getValue(obj)}
})

func getValue(obj) string {
   return obj.Spec.A + "," + obj.Spec.B + "," + obj.Spec.C
}

Client.List(xx, xxx, m)

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten