From 401b9c2336f61bec384de0b1a97ab70a58b5aa15 Mon Sep 17 00:00:00 2001 From: Aldo Lacuku Date: Thu, 19 Sep 2024 15:11:30 +0200 Subject: [PATCH] fix(falco): update broken link pointing to Falco docs After the changes made by the following PR to the Falco docs https://github.com/falcosecurity/falco-website/pull/1362 this commit updates a broken link. Signed-off-by: Aldo Lacuku --- charts/falco/CHANGELOG.md | 4 +++- charts/falco/README.gotmpl | 2 +- charts/falco/README.md | 2 +- 3 files changed, 5 insertions(+), 3 deletions(-) diff --git a/charts/falco/CHANGELOG.md b/charts/falco/CHANGELOG.md index 602a10ac3..4e3083286 100644 --- a/charts/falco/CHANGELOG.md +++ b/charts/falco/CHANGELOG.md @@ -16,7 +16,9 @@ numbering uses [semantic versioning](http://semver.org). The following PR in libs https://github.com/falcosecurity/libs/pull/1969 introduces a new platform for plugins that requires access to the proc filesystem. - +* fix(falco): update broken link pointing to Falco docs + After the changes made by the following PR to the Falco docs https://github.com/falcosecurity/falco-website/pull/1362 + this commit updates a broken link. ## v4.8.3 diff --git a/charts/falco/README.gotmpl b/charts/falco/README.gotmpl index a50c32d0b..f7d86d1d2 100644 --- a/charts/falco/README.gotmpl +++ b/charts/falco/README.gotmpl @@ -47,7 +47,7 @@ The cluster in our example has three nodes, one *control-plane* node and two *wo ### Falco, Event Sources and Kubernetes Starting from Falco 0.31.0 the [new plugin system](https://falco.org/docs/plugins/) is stable and production ready. The **plugin system** can be seen as the next step in the evolution of Falco. Historically, Falco monitored system events from the **kernel** trying to detect malicious behaviors on Linux systems. It also had the capability to process k8s Audit Logs to detect suspicious activities in Kubernetes clusters. Since Falco 0.32.0 all the related code to the k8s Audit Logs in Falco was removed and ported in a [plugin](https://github.com/falcosecurity/plugins/tree/master/plugins/k8saudit). At the time being Falco supports different event sources coming from **plugins** or **drivers** (system events). -Note that **a Falco instance can handle multiple event sources in parallel**. you can deploy Falco leveraging **drivers** for syscall events and at the same time loading **plugins**. A step by step guide on how to deploy Falco with multiple sources can be found [here](https://falco.org/docs/getting-started/third-party/learning/#falco-with-multiple-sources). +Note that **a Falco instance can handle multiple event sources in parallel**. you can deploy Falco leveraging **drivers** for syscall events and at the same time loading **plugins**. A step by step guide on how to deploy Falco with multiple sources can be found [here](https://falco.org/docs/getting-started/learning-environments/#falco-with-multiple-sources). #### About Drivers diff --git a/charts/falco/README.md b/charts/falco/README.md index 18b25e98d..b8c0490f3 100644 --- a/charts/falco/README.md +++ b/charts/falco/README.md @@ -47,7 +47,7 @@ The cluster in our example has three nodes, one *control-plane* node and two *wo ### Falco, Event Sources and Kubernetes Starting from Falco 0.31.0 the [new plugin system](https://falco.org/docs/plugins/) is stable and production ready. The **plugin system** can be seen as the next step in the evolution of Falco. Historically, Falco monitored system events from the **kernel** trying to detect malicious behaviors on Linux systems. It also had the capability to process k8s Audit Logs to detect suspicious activities in Kubernetes clusters. Since Falco 0.32.0 all the related code to the k8s Audit Logs in Falco was removed and ported in a [plugin](https://github.com/falcosecurity/plugins/tree/master/plugins/k8saudit). At the time being Falco supports different event sources coming from **plugins** or **drivers** (system events). -Note that **a Falco instance can handle multiple event sources in parallel**. you can deploy Falco leveraging **drivers** for syscall events and at the same time loading **plugins**. A step by step guide on how to deploy Falco with multiple sources can be found [here](https://falco.org/docs/getting-started/third-party/learning/#falco-with-multiple-sources). +Note that **a Falco instance can handle multiple event sources in parallel**. you can deploy Falco leveraging **drivers** for syscall events and at the same time loading **plugins**. A step by step guide on how to deploy Falco with multiple sources can be found [here](https://falco.org/docs/getting-started/learning-environments/#falco-with-multiple-sources). #### About Drivers