Syscall event drops on OpenShift platform

[christiaanvaken]

We have implemented Falco on OpenShift by using the Helm charts. Recently we have noticed a lot of syscall event drops, somethings the value of n_drops is over 100000. We have changed the resources section of the configuration to change rhe requests for cpu to 500m and the limits for the cpu to 1000m. The dropped events reduced a lot but we are still getting a lot of drops sometimes.

Is there any advice or solutions how to fix this on OpenShift?

[poiana]

@christiaanvaken: The label(s) kind/"help, kind/wanted" cannot be applied, because the repository doesn't have them.

In response to this:

/kind "help wanted"

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/test-infra repository.

[poiana]

@christiaanvaken: The label(s) kind/help, kind/wanted cannot be applied, because the repository doesn't have them.

In response to this:

/kind help wanted

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/test-infra repository.

[christiaanvaken]

@christiaanvaken: The label(s) kind/"help, kind/wanted" cannot be applied, because the repository doesn't have them.

@christiaanvaken: There is not a label identifying the kind of this issue.
Please specify it either using /kind <group> or manually from the side menu.

@poiana How do I do that?

[leogr]

Hi,

when opening an issue, there's a template that should be filled. Providing those details helps us to understand the issue. The template also includes instructions to set the correct labels. Please, do not remove it.

/kind bug

Anyway, in #1403 is present a handy checklist to debug kind of issues.
It could help in identifying the root cause of the syscall drops you are noticing.

[poiana]

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

[poiana]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh with /remove-lifecycle rotten.

Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Provide feedback via https://github.com/falcosecurity/community.

/lifecycle rotten

[poiana]

Rotten issues close after 30d of inactivity.

Reopen the issue with /reopen.

Mark the issue as fresh with /remove-lifecycle rotten.

Provide feedback via https://github.com/falcosecurity/community.
/close

[poiana]

@poiana: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue with /reopen.

Mark the issue as fresh with /remove-lifecycle rotten.

Provide feedback via https://github.com/falcosecurity/community.
/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/test-infra repository.