libs
libs copied to clipboard
falcosecurity
[TRACKING] Improve container engine state handling
Motivation
We have identified a few areas of improvements wrt to state handling during the container lookup cycle, see https://github.com/falcosecurity/libs/pull/1595#discussion_r1502988032.
This issue serves to track progress in this regard.
It is also related to https://github.com/falcosecurity/libs/issues/291.
@gnosek @therealbobo @mstemm @leogr
Please also explore https://github.com/falcosecurity/libs/pull/1707: It's incorrect to initialize a lookup to SUCCESSFUL, by the way. I believe this is the strongest indication of a very suboptimal shared design across the container engines we support.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale
We didn't get to this for libs 0.18. We need a lot more time to improve this as it will also need lots of testing.
We can try libs 0.19 or the following dev cycle.
Considering https://github.com/falcosecurity/falco/issues/3403, i think we can close this one. (i mean, no big effort/refactor/cleanup will be made on that area of sinsp since we are moving away from it).
/close
(Feel free to reopen if you feel this is still valuable!)
@FedeDP: Closing this issue.
In response to this:
Considering https://github.com/falcosecurity/falco/issues/3403, i think we can close this one. (i mean, no big effort/refactor/cleanup will be made on that area of sinsp since we are moving away from it).
/close
(Feel free to reopen if you feel this is still valuable!)
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.