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

rules: add support for k3s to containerd_activities macro #275

Merged

Conversation

kyrofa
Copy link
Contributor

@kyrofa kyrofa commented Mar 1, 2025

What type of PR is this?

/kind feature

Any specific area of the project related to this PR?

/area rules

Proposed rule maturity level

/area maturity-stable

K3s is a stripped down version of Kubernetes that bundles dependencies within it, including containerd. It puts containerd files (sockets, tmpmounts, snapshotter overlayfs, etc.) in namespaced, non-standard locations in an attempt to not interfere with a system-wide containerd installation. As a result, the "Clear Log Activities" rule triggers warnings for the bundled containerd. Fix that by including K3s' non-standard paths in the containerd_activities macro.

@poiana poiana added kind/feature New feature or request dco-signoff: yes area/rules area/maturity-stable See the Rules Maturity Framework labels Mar 1, 2025
@poiana poiana requested review from darryk10 and leodido March 1, 2025 23:31
@poiana
Copy link

poiana commented Mar 1, 2025

Welcome @kyrofa! It looks like this is your first PR to falcosecurity/rules 🎉

@poiana poiana added the size/XS label Mar 1, 2025
K3s is a stripped down version of Kubernetes that bundles dependencies
within it, including containerd. It puts containerd files (sockets,
tmpmounts, snapshotter overlayfs, etc.) in namespaced, non-standard
locations in an attempt to not interfere with a system-wide containerd
installation. As a result, the "Clear Log Activities" rule triggers
warnings for the bundled containerd. Fix that by including K3s'
non-standard paths in the containerd_activities macro.

Signed-off-by: Kyle Fazzari <[email protected]>
@kyrofa kyrofa force-pushed the feature/containerd_activities_k3s branch from d3e4882 to ba1f283 Compare March 1, 2025 23:33
@poiana
Copy link

poiana commented Mar 2, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: darryk10, kyrofa

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@poiana
Copy link

poiana commented Mar 2, 2025

LGTM label has been added.

Git tree hash: e1a86f63028b7c1035854914233f88af44613533

@poiana poiana added the approved label Mar 2, 2025
@poiana poiana merged commit 8e4ed0c into falcosecurity:main Mar 2, 2025
2 checks passed
@kyrofa kyrofa deleted the feature/containerd_activities_k3s branch March 2, 2025 22:55
@kyrofa
Copy link
Contributor Author

kyrofa commented Mar 2, 2025

Thanks folks! How do I actually track this to a release so I can know when I can drop my customized rules?

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

Successfully merging this pull request may close these issues.

3 participants