libs
libs copied to clipboard
falcosecurity
Container Engine Refactor (CRI)
Continue improvement suggestions from https://github.com/falcosecurity/libs/issues/1550
Prerequisites: More unit and e2e tests, especially also around cgroups.
Details to be added later.
Related:
- https://github.com/falcosecurity/libs/issues/1298
- https://github.com/falcosecurity/libs/pull/1228
- https://github.com/falcosecurity/falco/issues/2708
- https://github.com/falcosecurity/libs/issues/1115
@leogr @Andreagit97 @gnosek
/milestone 0.15.0
/assign
but it won't be just one PR or one person working on it, a collaborative effort is needed
Yes. So far we cleaned the API up, but we still need to improve the robustness and self-healing mechanisms if possible. I'll post more starting in 2 weeks ...
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
/milestone 0.19.0
Some incremental progress has been done here but container engines can still need some work
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
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.