-
Notifications
You must be signed in to change notification settings - Fork 912
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
WIP: [TRACKING] Falco 1.0 items #3148
Comments
/milestone 1.0.0 |
Issues go stale after 90d of inactivity. Mark the issue as fresh with Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with Provide feedback via https://github.com/falcosecurity/community. /lifecycle stale |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. Mark the issue as fresh with Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with Provide feedback via https://github.com/falcosecurity/community. /lifecycle stale |
/remove-lifecycle stale |
Motivation
We recently published the high-level roadmap for Falco 1.0. Although we don't have a target date yet, we already have some items around, planned for 1.0, that directly affect the Falco application. This issue only aims to track these items/issues.
A dedicated GitHub issue is available only for deprecations we may want to introduce in Falco 1.0
Falco 1.0.0 items
falco.yaml
structure #3254metrics
framework future refactors / cleanups #3194container.id
andcontainer.name
libs#2057The text was updated successfully, but these errors were encountered: