Skip to main content
In this lesson you’ll learn how to deploy Falco with Falco Sidekick and its optional web UI using Helm. Falco Sidekick receives Falco events and forwards them to external systems (Slack, Teams, Datadog, etc.) while also providing a searchable UI to inspect alerts by severity, rule, namespace, pod, and other fields. Repository and reference:
A screenshot of a Falco blog post titled "Extend Falco outputs with falcosidekick," showing the article header, a diagram labeled "Falco extended architecture," and site navigation/sidebar. The page also includes edit links on the right and a small circular profile photo in the top-right corner.
Overview
  • Falco Sidekick acts as a bridge: it consumes Falco alerts (via stdout, file, gRPC, syslog, HTTP) and forwards them to multiple outputs.
  • The optional Falco Sidekick web UI displays recent events and supports filtering and search for rapid investigation.
  • Helm is used to install Falco, Falco Sidekick, and the UI into a Kubernetes cluster.
Helm charts package Kubernetes manifests and default configuration. Installing the Falco chart with falcosidekick.enabled=true deploys Sidekick alongside Falco agents. Use the Sidekick web UI for interactive event exploration.
Quick Install (namespace, repo, install with UI)
Optional: If you want Slack notifications, include your Slack webhook URL during install:
Helm & RPM/YUM Analogy
  • Helm charts are packages containing Kubernetes manifests and default configuration (ConfigMaps, Deployments, Services, Ingress, etc.).
  • Helm CLI is the Kubernetes package manager that installs chart “releases” into your cluster.
  • Think of Helm charts like RPM packages and Helm like YUM: YUM resolves dependencies and installs RPMs; Helm resolves chart requirements and deploys resources.
Helm installation (example script)
Example output after installing Helm (your version may differ):
Helm v3 removed Tiller and runs client-side, directly interacting with the Kubernetes API. Ensure your kubeconfig and cluster permissions are correct before installing charts.
Installing Falco + Falco Sidekick + Web UI (step-by-step)
  1. Create the falco namespace and add the Falco Helm repo (see the quick install above).
  2. Install the Falco chart enabling Falco Sidekick and the web UI:
Sample install output (trimmed):
Verify installation
Example kubectl -n falco get all output (trimmed)
Expose the UI (optional)
  • By default the Falco Sidekick UI service is ClusterIP. To access it externally from a browser, change the service to NodePort.
Edit the service:
Change the spec to:
After saving, check the assigned NodePort in the service listing (e.g., 2802:30576/TCP).
Exposing the Falco UI via NodePort or LoadBalancer can expose event data externally. Protect access with network controls, authentication, or by using an internal ingress. Do not expose sensitive operational logs publicly.
Accessing the UI
  • Use the node IP (or node DNS) and the assigned NodePort, then open the UI path in your browser:
    • Example: http://<node-ip>:30576/UI (replace <node-ip> and port with your environment values)
  • The UI shows recent Falco alerts and provides filters: rule, severity, namespace, pod, container, and timestamp.
Example Falco event snippets shown in the UI
  • Terminal shell spawned in container:
  • Privileged container started:
These UI entries mirror the detailed Falco log fields, but with search and filtering capabilities that accelerate incident investigation. Commands summary Next steps & recommendations
  • If you want Slack notifications, reinstall or upgrade the chart with your Slack webhook:
  • Secure the UI: use an internal-only service, restrict access with network policies, or place the UI behind an authenticated ingress.
  • Explore additional Falco Sidekick outputs (Teams, Datadog, PagerDuty, Elasticsearch) via the Sidekick configuration documented in the Falco Sidekick repo.
That’s it — deploy Falco with Sidekick and the UI using Helm to get searchable alerting and flexible notifications for your Kubernetes workloads.

Watch Video