Wallarm Sidecar

Kubernetes Helm chart that injects an NGINX-based Wallarm WAF sidecar proxy into application pods to filter and mitigate malicious traffic.

  • Infrastructure
  • Network Services
  • Security
Kubernetes Helm chart that injects an NGINX-based Wallarm WAF sidecar proxy into application pods to filter and mitigate malicious traffic.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

50/100 Fair

Maintained
84last commit 17 days ago
Popular
144 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today

GitHub stars
4
Open issues
5
Last commit
2026-11-04
Latest release
helm-chart-5.3.10
License
Apache-2.0
Activity
rising

Checked 14 days ago - source: GitHub (wallarm/sidecar)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Make sure it can reach your app Before you start, check that the target address and port match your app, like the example's http://localhost:8080. If the tester cannot connect, its pre-checks fail and you get no useful WAF (web application firewall) results. source
  • Match raw request fields exactly If you create a raw HTTP test, set the method, path, headers, and body exactly, and keep the multipart boundary (the label that separates form-data parts) in the body matching the Content-Type header (which says the body is form-data). If they do not line up, the tester sends the wrong request and results can look broken or bypassed. source
  • Read the pre-check lines first The log first reports whether WAF, WebSocket (a persistent two-way connection), and gRPC (a fast request protocol) were found. If a line says not available or not identified, that feature could not be tested, so do not mistake it for a WAF failure. source

Fetched 41 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

What must I handle in a self-hosted Wallarm deployment?

You are responsible for installing and operating the Wallarm Node within your infrastructure. The documentation says this gives you full control over configuration, networking, and scaling.

Which Kubernetes component injects the Wallarm sidecar into a pod?

The wallarm-sidecar-controller is the mutating admission webhook that injects Wallarm sidecar resources into the pod.

Answers sourced from docs.wallarm.com, docs.wallarm.com

Community

Collected 48 days ago - public community threads