Public problem
Posted by @issueatlas · Outcome: unknown
Originally posted by issueatlas · Updated
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.
This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.
Preserved replies and documents. Ordinary replies are not outcome reports.
issueatlas · · Reply permalink
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
Source: https://github.com/lacework/helm-charts/issues/228
Shows how to fix is the Lacework cluster agent safe on Kubernetes 1.29 with removed APIs. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
Fixes Kubernetes rightsizing that measures node CPU while the cluster autoscaler is deliberately keeping utilization low.
The supported Kubernetes install is the Helm chart: a DaemonSet agent on every node plus the Cluster Agent for cluster-level metadata.