Ansible-operator stuck on queries to cache since version 1.38.

Bug Report

We use Asnible SDK Operator for deployment of components to K8S cluster. We use custom docker image, that is based on the official image (we just add Ansible playbooks inside). Since versio 1.38.0 we started to receive for one type of playbook messages:

{"level":"info","ts":"2025-10-08T10:48:53Z","logger":"proxy","msg":"Read object from cache","resource":{"IsResourceRequest":true,"Path":"/apis/apps/v1/namespaces/istio-system/replicasets","Verb":"list","APIPrefix":"apis","APIGroup":"apps","APIVersion":"v1","Namespace":"istio-system","Resource":"replicasets","Subresource":"","Name":"","Parts":["replicasets"]}}

These messges are repeating several times every second and blocks the ansible playbook on that specific step.

What did you do?

This Ansible task is the last before the messages start.

    - name: Apply Istio configuration to the cluster
      shell: |
        {{ istioctl_dest }}/istioctl manifest apply -f "{{ config_manifests }}/config-{{ app_name }}.yaml" --namespace istio-system --verify -y --readiness-timeout 60m

What did you expect to see?

In image based on SDK Operator 1.37.2, the steps performs without issues and the playbook continues with the following steps. In Ansible SDK Operator image v1.38 and higher (up to 1.41.0), the step metnioned above stucks and still repeating the message metioned. I would like to see the same behavior like in version 1.37, so the playbook will continue and not stuck with these messages.

What did you see instead? Under which circumstances?

The same playbook that works in v1.37, stuck at the the task in v1.38 and higher.

Environment

Kubernetes cluster type:

K8S 1.29 - 1.33 (deployed via Kubespray)

$ operator-sdk version

Mentioned above. Image version 1.37.2 and 1.38.0 and higher
ansible-operator version: "v1.37.2", commit: "dc6090705b01925cfa130b25bf7ca1d7ff7a5430", kubernetes version: "v1.31.0", go version: "go1.23.4", GOOS: "linux", GOARCH: "amd64"
Exampel of non working one:
ansible-operator version: "v1.41.0", commit: "8e923f25256c2b64c85a2c9dfabd157e8f880ea8", kubernetes version: "v1.32.0", go version: "go1.24.4", GOOS: "linux", GOARCH: "amd64" b

I can provide more info if necessary.
Thank you

Start by comparing ansible-operator v1.37.2 with v1.38 and later around the proxy cache handling for the repeated ReplicaSet list request. Reproduce the Ansible task running istioctl manifest apply with the supplied Kubernetes versions; done means the task completes and the playbook continues without repeated cache messages.