Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document Deployment recommendations for k8saudit plugin vs knode / DaemonSet deployment for syscalls monitoring #1119

Open
incertum opened this issue Aug 3, 2023 · 11 comments

Comments

@incertum
Copy link
Contributor

incertum commented Aug 3, 2023

/area documentation

What would you like to be added:

@leogr as discussed in the core maintainers meeting 2023-08-03 try to improve docs on website wrt deployment of k8saudit plugins on control node of cluster vs DaemonSet / syscalls monitoring on the knodes

@incertum
Copy link
Contributor Author

incertum commented Aug 3, 2023

/assign @leogr

@Issif
Copy link
Member

Issif commented Aug 3, 2023

The first should be to specify for each plugin, in the registry, the kind of expected deployment (daemonset, 1 replica deployment, multi-replicas deployment). This information could be part of the yaml to list the existing plugins.

@poiana
Copy link

poiana commented Nov 1, 2023

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

@leogr
Copy link
Member

leogr commented Nov 8, 2023

/remove-lifecycle stale

@poiana
Copy link

poiana commented Feb 6, 2024

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

@leogr
Copy link
Member

leogr commented Feb 8, 2024

/remove-lifecycle stale

cc @LucaGuerra @mikegcoleman

@leogr
Copy link
Member

leogr commented Mar 26, 2024

btw, it is already documented in the helm chart
https://github.com/falcosecurity/charts/tree/master/charts/falco#deploying-falco-in-kubernetes
It can be a source of inspiration to do the same in the official documentation.

@poiana
Copy link

poiana commented Jun 24, 2024

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

@leogr
Copy link
Member

leogr commented Jun 24, 2024

/remove-lifecycle stale
/assign @LucaGuerra

@poiana
Copy link

poiana commented Sep 22, 2024

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

@leogr
Copy link
Member

leogr commented Sep 23, 2024

/remove-lifecycle stale

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants