Maik

> @VF-mbrauer - just wondering if you saw my reply or not, and whether these changes are still required? > > Thanks Hi @nabadger, apologize for the late reply. I...

Hi @nabadger, yes of course. Feel free to amend for me and get it merged. Then we can finally close this thread. Thanks.

@nabadger Any news here. Did you amend and merged that in the meantime?

Any news here as this is quite important that we have with the latest release the most recent OS base image applied.

i have also the same issue? Do we still get support here? Support zone got a bit abandoned. @alexryd Can you help us here?

@alexryd is that plugin still supported? If not then we would need to change for a one which still has a proper lifecycle. Thanks.

Has that issue been solved? I am still getting with huge, loaded nodes the error: ``` Defaulted container "falco" out of: falco, falcoctl-artifact-follow, falco-driver-loader (init), falcoctl-artifact-install (init) Thu Mar 23...

@jasondellaluce, yes it will go first run into an OOM and then Restart, after some time it gets stalled into **"CrashLoopBackOff"** ``` falco-7sgbh 2/2 Running 0 88m falco-fd9kz 1/2 CrashLoopBackOff...

Sounds like the same already discussed here: https://github.com/ansible/ansible/issues/81830 But I use a higher version of **ansible-core** and it still is not fixed. @sivel FYI.

@chen-keinan I guess we can close? Do we?