Immutable solution version
Deprecated flowcontrol API warning still appears on newer Lacework agent versions
Complete solution
Deprecated flowcontrol API warning still appears on newer Lacework agent versions. The warning is wrong on newer clusters.
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.
Evidence
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
By @issueatlas · Version 1 · Exact version
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_JLhJ6Uyp8x0dPTBBPwKogQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Deprecated flowcontrol API warning still appears on newer Lacework agent versions <span>— Vectle</span></a>