[Tracking 0.37.1] Falco 0.37.1

[Andreagit97]

Falco 0.37.1 Release

Will keep this issue updated with the current status and progress.

Date

Target release date:

Release Steps

The process is described in this document.

External dependencies

Preview Give feedback

1. falcoctl -> v0.7.2: https://github.com/falcosecurity/falcoctl/releases/tag/v0.7.2
2. libs -> 0.14.3: https://github.com/falcosecurity/libs/releases/tag/0.14.3
3. drivers -> NO CHANGES
4. rules -> NO CHANGES
5. plugins bump -> NO CHANGES

Manual Testing Action Items

Preview Give feedback

1. Running Falco on Kubernetes with the official Helm Charts
2. Running Falco from RPM and DEB artifacts
3. Running Falco in a container with the official images
4. Running/fuzzing Falco with multiple event sources active in parallel
5. Running/fuzzing Falco with variable syscall buffer dimension
6. Running Falco in all officially-supported architectures (x86_64, ARM64)
7. Running Falco with the supported drivers (kmod, modern eBPF, eBPF, gVisor, trace files)
8. Test Falco with event generator
9. Test that plugins are correctly loaded
10. Test memory and CPU usage (with Valgrind and other tools)
11. Test latest version of driver loader
12. Test that k8smeta plugin works as expected
13. Test that all Falco CLI options work as expected
14. Check that Falco log messages are correct and consistent
15. Test that Falco ruleset loading and validation works as expected
16. Test Falco with Gvisor

Action Items

• Pre-Release
  • Milestone
  • Code freeze in falcosecurity/falco
  • Open release branch in Falco and protect it
  • See External dependencies task lists
  • Prebuilt drivers publish
  • Code thaw in falcosecurity/falco
  • Changelog on the release branch
  • cherry-pick the changelog on master
• Release
  • Github Release in the Falco repo
• Website
  • Create new snapshot
    • Protect snapshot branch
  • Merge the release blog post
  • Merge all necessary documentation PRs
• Helm
  • Release a new helm chart version
  • Update helm chart documentation
  • Add instructions to the Helm chart readme about how to switch images if necessary
• Announcements
  • mailing list
  • blog post
  • slack channel
• Post-Release
  • Archive community call meeting notes
  • Close the resolved issues after the tag and move the unresolved ones under a new milestone
  • Update supported fields and syscall documentation
  • add Falco version to the rules CI: update(ci): add Falco 0.37.1 to FALCO_VERSIONS. rules#228

Miscs

/milestone 0.37.1

/kind documentation

PRs that should be cherry-picked into the release branch

Synced with:

---

Breaking changes

• supporting dynamic linking for libelf we introduce breaking changes
  • Falco tar.gz needs libelf installed on the system, since it is no longer shipped statically inside the Falco binary
  • Falco musl packages won't be shipped anymore

[FedeDP]

Tag created: https://github.com/falcosecurity/falco/releases/tag/0.37.1-rc1
Waiting on CI: https://github.com/falcosecurity/falco/actions/runs/7872714349

It spots libs 0.14.3 (https://github.com/falcosecurity/libs/releases/tag/0.14.3) and falcoctl v0.7.2 (https://github.com/falcosecurity/falcoctl/releases/tag/v0.7.2).

[FedeDP]

4 PRs to go:

• update(falco): bump falco to 0.37.1 charts#622
• update(ci): add Falco 0.37.1 to FALCO_VERSIONS. rules#228
• chore(config): update Falco version number for 0.37.1 falco-website#1270
• chore(meeting-notes): archive content of community calls. community#205

[FedeDP]

/close

[poiana]

@FedeDP: Closing this issue.

In response to this:

/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.