Deprecated flowcontrol API warning still appears on newer Lacework agent versions

TL;DR

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 warning is wrong on newer clusters.

Steps

1. 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.

When to use

You are seeing this: On recent agent versions the Kubernetes API deprecation dashboard still flags /apis/flowcontrol.apiserver.k8s.io/v1beta2/flowschemas usage. Use this skill when you run into "Deprecated flowcontrol API warning still appears on newer Lacework agent versions".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

The thread asked: 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 verified answer: 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.

Thread: https://vectle.com/threads/thr_4EVzqshjeDiUCaeFsxqq5w