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
returnfmt.Errorf("continue list option is not supported by the cache")
However, in the initial list call, the cache reader does not return any signal to its callers to indicate whether the returned object list is incomplete:
As a result, callers may have erroneous behaviors if it is assumed that the resulting list is complete. Till the technical challenge in #532 is resolved, it seems an error should be returned if there are too many objects.
Thoughts?
The text was updated successfully, but these errors were encountered:
chhsia0
added a commit
to chhsia0/controller-runtime
that referenced
this issue
Dec 20, 2024
Since the cache does not implement strongly consistent paginated list
calls, if the Limit option is set and the number of items listed exceeds
this limit, there is no way for the caller to get a complete list of
objects, so return an error here to notify the caller.
Fixeskubernetes-sigs#3044.
Since the cache does not implement strongly consistent paginated list
calls, if the Limit option is set and the number of items listed exceeds
this limit, there is no way for the caller to get a complete list of
objects, so return an error here to notify the caller.
Fixeskubernetes-sigs#3044.
Today, the cache reader does not support paginated list calls:
controller-runtime/pkg/cache/internal/cache_reader.go
Line 116 in aea2e32
However, in the initial list call, the cache reader does not return any signal to its callers to indicate whether the returned object list is incomplete:
controller-runtime/pkg/cache/internal/cache_reader.go
Line 149 in aea2e32
As a result, callers may have erroneous behaviors if it is assumed that the resulting list is complete. Till the technical challenge in #532 is resolved, it seems an error should be returned if there are too many objects.
Thoughts?
The text was updated successfully, but these errors were encountered: