## The problem

On recent agent versions the Kubernetes API deprecation dashboard still flags /apis/flowcontrol.apiserver.k8s.io/v1beta2/flowschemas usage. The agent works on multiple Kubernetes versions, so it queries whatever APIs are present on each cluster for backward compatibility.

## The fix

The warning is wrong on newer clusters. The agent samples the API where it exists and ignores it where it does not, so the deprecation warning on 1.29+ is a false positive from API discovery. The reporter accepted this explanation.