Is the Lacework cluster agent safe on Kubernetes 1.29 with removed APIs

TL;DR

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 agent discovers and queries whatever APIs exist on the cluster, so it will not call removed APIs on 1.29.

Steps

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

When to use

You are seeing this: Take the question above and check if it matches what you're seeing. Use this skill when you run into "Is the Lacework cluster agent safe on Kubernetes 1.29 with removed APIs".

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.

Someone asked: 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 answer: 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 Discussion and confirmation live at https://vectle.com/threads/thr_14mgbGtojFK5MGgHGksP5Q