-
Notifications
You must be signed in to change notification settings - Fork 919
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Since upgrading EKS to 1.13 falco lost ability to detect pod name #865
Comments
DaemonSet:
|
Configmap:
|
It was working perfectly before upgrade from EKS 1.11 to 1.13 |
Thanks for reporting this @michalzxc - I dibs on this, let's see if I can reproduce. /assign @fntlnz |
I am also now seeing this same issue however we are on EKS 1.14.7., Falco 0.17.1, image 0.18.0 It took a weekend for falco to start doing this. Not sure if its related but I have another ticket #961
|
the same behavior for bare-metal cluster. |
For bare-metal,ka.req.container.image and ka.req.container.image.repositoryas well: |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
We're also seeing this on GKE
|
We've been working on PR #1133 lately. It solves the issue you're reporting as you can see from the following outputs (eg.,
Also, the issue is solved also when running Falco as a docker container (and not in Kubernetes). As you can see from the following outputs,
Would be cool if you give it a shoot using one of the temp artifacts available here. Otherwise, you can try it as soon as we merge PR 1133 using the |
What happened:
It seems Falco lost ability to detect pod name and thinks that operations happens on host
Loots of alerts like that:
The only Debian is inside docker images, there is no /etc/logrotate.d/dpkg on any host, so "container=host" is false without doubt
What you expected to happen:
I didn't expected to see logs like above, it shows like hundred-ish of them per second
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
falco --version
): 0.17.1cat /etc/os-release
):uname -a
):The text was updated successfully, but these errors were encountered: