You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After discussion in the following issue: falcosecurity/charts#754 , what I could gather is that the new linux_hostinfo platform provides additional information to plugins should they need it.
However, Falco being a fairly general tool to process event streams and apply rules to them, plugins can be made to target event streams where the hostinfo of where Falco is running is irrelevant, or of very little concern.
I think it would be great if this could be optional, so that, when deployed to Kubernetes, hostPath is not required.
Feature
Make the new linux_hostinfo platform optional so that it can be turned off and hostPath isn't required.
Alternatives
Keep hostPath even though it is not required by plugin.
The text was updated successfully, but these errors were encountered:
Motivation
After discussion in the following issue: falcosecurity/charts#754 , what I could gather is that the new linux_hostinfo platform provides additional information to plugins should they need it.
However, Falco being a fairly general tool to process event streams and apply rules to them, plugins can be made to target event streams where the hostinfo of where Falco is running is irrelevant, or of very little concern.
I think it would be great if this could be optional, so that, when deployed to Kubernetes,
hostPath
is not required.Feature
Make the new linux_hostinfo platform optional so that it can be turned off and
hostPath
isn't required.Alternatives
Keep
hostPath
even though it is not required by plugin.The text was updated successfully, but these errors were encountered: