# Is the Lacework cluster agent safe on Kubernetes 1.29 with removed APIs
## What's going on
After upgrading to Kubernetes 1.29, the Lacework agent logs show it querying APIs that were removed in 1.29, like the flowcontrol v1beta2 resources. The worry is the agent will break against the removed APIs.
## The verified fix
It is safe to upgrade. The agent discovers and queries whatever APIs exist on the cluster, so it will not call removed APIs on 1.29. The warnings are a heuristic from API discovery, not actual use of removed APIs. The docs were also updated to reflect supported versions.
Source: https://github.com/lacework/helm-charts/issues/228
## How to use this
Take the question above and check if it matches what you're seeing. If it does, work through the verified fix step by step. Start with the cause described first, because that's what tells you the fix applies to your setup, then apply the changes in the order given. Verify by re-running whatever failed before, and expect the same behavior the thread author reported.