Falco 0.39.0 Release

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

Date

Target release date: September 30th 2024

Release Steps

The process is described in this document.

## External dependencies
- [x] falcoctl -> [v0.10.0](https://github.com/falcosecurity/falcoctl/releases/tag/v0.10.0)
- [x] libs 0.18.0 -> [0.18.0](https://github.com/falcosecurity/libs/releases/tag/0.18.0)
- [ ] drivers -> [7.3.0+driver](https://github.com/falcosecurity/libs/releases/tag/7.3.0%2Bdriver)
- [x] rules -> [3.2.0](https://github.com/falcosecurity/rules/releases/tag/falco-rules-3.2.0)
- [ ] plugins bump

## Manual Testing Action Items
- [ ] Running Falco on Kubernetes with the official Helm Charts
- [ ] Running Falco from RPM and DEB artifacts
- [ ] Running Falco in a container with the official images
- [ ] Running/fuzzing Falco with multiple event sources active in parallel
- [ ] Running/fuzzing Falco with variable syscall buffer dimension
- [ ] Running Falco in all officially-supported architectures (x86_64, ARM64)
- [ ] Running Falco with the supported drivers (kmod, modern eBPF, eBPF, gVisor, trace files)
- [ ] Test Falco with event generator
- [ ] Test that plugins are correctly loaded
- [ ] Test memory and CPU usage (with Valgrind and other tools)
- [ ] Test latest version of driver loader
- [ ] Test that `k8smeta` plugin works as expected
- [ ] Test that all Falco CLI options work as expected
- [ ] Check that Falco log messages are correct and consistent
- [ ] Test that Falco ruleset loading and validation works as expected
- [ ] Test Falco with Gvisor

Action Items

[ ] Pre-Release
- [x] Milestone
- [x] Code freeze in falcosecurity/falco
- [x] 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
[ ] 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:

Miscs

/milestone 0.39.0

/assign alacuku

/kind documentation

Release blocking PRs

@alacuku: You must be a member of the falcosecurity/falco-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your maintainers of falcosecurity/falco and have them propose you as an additional delegate for this responsibility.

In response to [this](https://github.com/falcosecurity/falco/issues/3326): ># Falco 0.39.0 Release > >Will keep this issue updated with the current status and progress. > >## Date > >Target release date: September 30th 2024 > >## Release Steps > >The process is described in [this document](https://github.com/falcosecurity/falco/blob/master/RELEASE.md). > >```[tasklist] >## External dependencies >- [] falcoctl >- [] libs >- [] drivers >- [] rules >- [] plugins bump >``` > >```[tasklist] >## Manual Testing Action Items >- [] Running Falco on Kubernetes with the official Helm Charts >- [] Running Falco from RPM and DEB artifacts >- [] Running Falco in a container with the official images >- [] Running/fuzzing Falco with multiple event sources active in parallel >- [] Running/fuzzing Falco with variable syscall buffer dimension >- [] Running Falco in all officially-supported architectures (x86_64, ARM64) >- [] Running Falco with the supported drivers (kmod, modern eBPF, eBPF, gVisor, trace files) >- [] Test Falco with event generator >- [] Test that plugins are correctly loaded >- [] Test memory and CPU usage (with Valgrind and other tools) >- [] Test latest version of driver loader >- [] Test that `k8smeta` plugin works as expected >- [] Test that all Falco CLI options work as expected >- [] Check that Falco log messages are correct and consistent >- [] Test that Falco ruleset loading and validation works as expected >- [] Test Falco with Gvisor >``` > >## Action Items > >- [] **Pre-Release** > - [x] 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 >- [] **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: > >## Miscs > >/milestone 0.39.0 > >/assign alacuku > >/kind documentation > >## Release blocking PRs Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.

falcosecurity / falco