chore(plugins/k8saudit): bump to v0.16.1#1234
chore(plugins/k8saudit): bump to v0.16.1#1234IdeoG wants to merge 1 commit intofalcosecurity:mainfrom
Conversation
|
Welcome @IdeoG! It looks like this is your first PR to falcosecurity/plugins 🎉 |
0670915 to
51054ce
Compare
|
Hey, thank you for this contribution! |
ekoops
left a comment
There was a problem hiding this comment.
For to bother you again with this, but we should replace ## dev build (unreleased) with ## v0.17.0. Moreover, the second commit is not DCO-signed. I suggest to replace the aforementioned heading and squash the two commits into a single signed commit.
57dce85 to
d755d76
Compare
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: IdeoG The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Thanks for the good catch! I've replaced the heading with |
94c4845 to
75c9e9b
Compare
|
Oh sorry, I've just notice that the only change we made was adding a backward-compatible fix. Unfortunately we must bump the version to |
Signed-off-by: Aleksei Gaibura <agaibura@tripleten.com>
75c9e9b to
a0c533a
Compare
|
Thank you for your quick review. Valid point. |
Includes panic recovery for fastjson on large payloads (commit 3a2616d). Fixes crash when parsing truncated CloudWatch audit events.
Ref: #1098
What type of PR is this?
/kind bug
Any specific area of the project related to this PR?
/area plugins
What this PR does / why we need it:
Bump k8saudit to v0.17.0. This version includes panic recovery (commit 3a2616d) around fastjson parsing, which prevents Falco from crashing when processing truncated or oversized CloudWatch audit events (~1MB). Without this, the k8saudit-eks plugin panics and restarts on every truncated event.
Which issue(s) this PR fixes:
Fixes #1098
Special notes for your reviewer:
This is a version bump only. The panic recovery logic was merged in commit 3a2616d (Jan 23, 2026). k8saudit-eks will need a follow-up PR to bump its go.mod to v0.17.0 and release v0.11.0.