Openshift k8s cluster API Server is not honoring limit parameters in API call

[gdandu-uptycs]

What happend?:

In openshift version 4.15.0 based k8s cluster we are using k8s.io/client-go v0.28.6 in our application. When we call listing APIs for resources (like pods), the passed limit parameter of 100 is returning 814 rows. This is causing resources issues in our application. See the below our logs for reference/example

time="2025-03-18T10:31:08Z" level=info msg="Number of rows received from kube api-server is 814, remaining row count is 161, computed optimal row limit is 500, current list iteration is 1, max list iteration is 1000" resource=pods

What did you expect to happen?
The Openshift API Server should return less than or equal to number of rows requested in the API call.

How can we reproduce it (as minimally and precisely as possible)?

options := metav1.ListOptions{Limit: 100}
pods, err := k8s.GetClient().CoreV1().Pods(metav1.NamespaceAll).List(ctx, options)

[gdandu-uptycs]

Here is the oc version

oc version
Client Version: 4.16.13
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: 4.15.0
Kubernetes Version: v1.28.6+6216ea1