You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've encountered a peculiar issue with the Falcon sensor in our Kubernetes environment. When using the cluster autoscaler to scale nodes up or down, the sensor appears to interfere with proper node termination.
Specifically, when a node is marked for scale-down, the Falcon sensor prevents it from being fully terminated. As a result, all containers and pods on that node remain stuck in a Terminating state. This behavior generates unnecessary alerts and disrupts our scaling workflows.
E0519 08:33:33.288287 2058 kubelet.go:2027] "Unhandled Error" err="[failed to \"KillContainer\" for \"falcon-node-sensor\" with KillContainerError: \"rpc error: code = Unknown desc = failed to kill container \\\"22e8add0a093d2d26d9c55b12fa0a4c07aeb687b6e57124b4c41da28a565be46\\\": unknown error after kill: runc did not terminate successfully: exit status 1: unable to signal init: operation not permitted\\n: unknown\", failed to \"KillPodSandbox\" for \"81d83ad2-5c47-4c8e-a90b-1fe492ae0865\" with KillPodSandboxError: \"rpc error: code = Unknown desc = failed to stop container \\\"22e8add0a093d2d26d9c55b12fa0a4c07aeb687b6e57124b4c41da28a565be46\\\": failed to kill container \\\"22e8add0a093d2d26d9c55b12fa0a4c07aeb687b6e57124b4c41da28a565be46\\\": unknown error after kill: runc did not terminate successfully: exit status 1: unable to signal init: operation not permitted\\n: unknown\"]" logger="UnhandledError"
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi Team
We've encountered a peculiar issue with the Falcon sensor in our Kubernetes environment. When using the cluster autoscaler to scale nodes up or down, the sensor appears to interfere with proper node termination.
Specifically, when a node is marked for scale-down, the Falcon sensor prevents it from being fully terminated. As a result, all containers and pods on that node remain stuck in a Terminating state. This behavior generates unnecessary alerts and disrupts our scaling workflows.
E0519 08:33:33.288287 2058 kubelet.go:2027] "Unhandled Error" err="[failed to \"KillContainer\" for \"falcon-node-sensor\" with KillContainerError: \"rpc error: code = Unknown desc = failed to kill container \\\"22e8add0a093d2d26d9c55b12fa0a4c07aeb687b6e57124b4c41da28a565be46\\\": unknown error after kill: runc did not terminate successfully: exit status 1: unable to signal init: operation not permitted\\n: unknown\", failed to \"KillPodSandbox\" for \"81d83ad2-5c47-4c8e-a90b-1fe492ae0865\" with KillPodSandboxError: \"rpc error: code = Unknown desc = failed to stop container \\\"22e8add0a093d2d26d9c55b12fa0a4c07aeb687b6e57124b4c41da28a565be46\\\": failed to kill container \\\"22e8add0a093d2d26d9c55b12fa0a4c07aeb687b6e57124b4c41da28a565be46\\\": unknown error after kill: runc did not terminate successfully: exit status 1: unable to signal init: operation not permitted\\n: unknown\"]" logger="UnhandledError"Beta Was this translation helpful? Give feedback.
All reactions