Closed jamesez closed 9 months ago
Working through https://github.com/CrowdStrike/Cloud-AWS/blob/main/Container%20Security/kernel-eks-implementation-guide.md, it says to exec into one of the CS pods and run lsmod, but the current image doesn't seem to include one:
lsmod
) kubectl -n falcon-system exec -i -t falcon-helm-falcon-sensor-2qkg6 -- /bin/sh Defaulted container "falcon-node-sensor" out of: falcon-node-sensor, init-falconstore (init) sh-4.4# lsmod sh: lsmod: command not found
I was able to verify it by launching a debian pod, installing kmod, but the docs are incorrect.
debian
kmod
"Fixing" this by just removing the documentation is deeply dissatisfying, and speaks to engineering time being misallocated.
Working through https://github.com/CrowdStrike/Cloud-AWS/blob/main/Container%20Security/kernel-eks-implementation-guide.md, it says to exec into one of the CS pods and run
lsmod
, but the current image doesn't seem to include one:I was able to verify it by launching a
debian
pod, installingkmod
, but the docs are incorrect.