KubeArmor
kubearmor.io
- Free plan
- Linux
- API
- Self-hosted
What KubeArmor is
KubeArmor is an open-source runtime security system for enforcing policies on cloud-native workloads as they run. It uses Linux Security Modules such as AppArmor, SELinux, and BPF-LSM, with eBPF for alerts and telemetry that carries container, pod, and namespace identities. Policies can restrict process execution, file access, networking operations, and resource use. Container policies can Allow, Audit, or Block actions, with Block as the default; system-call monitoring supports audit only. Kubernetes policies can use workload metadata and pod labels to select targets, while rules can match paths, network protocols, capabilities, and system calls. The support matrix covers Kubernetes, non-Kubernetes containers, virtual machines, and bare-metal hosts, with availability varying by environment, operating system, architecture, and enforcement mode. Listed Kubernetes environments include GKE, AKS, OKE, IKS, EKS, OpenShift, Rancher, and DigitalOcean Kubernetes. Project repositories include integrations for OpenTelemetry, Prometheus, Kafka, Grafana, ELK dashboards, GitHub Actions, and Rancher. KubeArmor is a community-governed CNCF Sandbox project. Its installation guide uses Helm and kubectl.
Who it suits
KubeArmor suits teams hardening cloud containers, IoT and edge workloads, or 5G networks. It is relevant where runtime policy enforcement is needed across Kubernetes or other supported workloads.
Good to know, and what to watch
- Open-source runtime security system
- Policies can block process and file activity
- Targets Kubernetes workloads using labels
- Supports containers, virtual machines, and bare metal
- Includes telemetry and policy violation logging
- System-call monitoring supports audit only
- Some environments are observability-only
- VMware Tanzu support entries are under construction
Plans
Every plan and priceKubeArmor
Open source
The Club's review
KubeArmor is a free, open-source runtime security system for teams running Kubernetes, containers, virtual machines, or bare-metal workloads they control. It suits security and platform engineers who want workload-aware Linux policy enforcement rather than a hosted service. The main reason to choose it is granular runtime blocking across processes, files, networks, and resources; the main caution is that enforcement depends heavily on the operating system, architecture, and mode in your deployment.
Overview
KubeArmor hardens cloud-native workloads by applying security rules at runtime. It is community-governed and a CNCF Sandbox project, with use cases spanning cloud containers, edge and IoT systems, and 5G networks. Because it is self-hosted, your team owns installation, policy design, upgrades, and operational support.
The project supports Kubernetes workloads as well as non-Kubernetes containers, virtual machines, and bare-metal hosts. Kubernetes installation is delivered through the KubeArmor Operator, using Helm and kubectl. The support matrix should be a release gate: some combinations provide observability only, including RHEL or CentOS 8.4 and earlier on Kubernetes and Oracle Ampere, while VMware Tanzu entries are under construction.
Key features
KubeArmor uses Linux Security Modules—AppArmor, SELinux, and BPF-LSM—to enforce policy. Container rules offer Allow, Audit, and Block actions, with Block as the default. You can match process paths and directories, file paths and directories, network protocols, capabilities, and system calls, then restrict execution, file access, networking, and resource use inside a workload.
System-call monitoring is audit-only, so KubeArmor can show that behavior without preventing it. That distinction matters for teams looking for hard prevention at the syscall layer. For Kubernetes, policies can use metadata and select pods with labels or label expressions, tying controls to workload identity instead of fragile host-specific targeting.
eBPF telemetry records policy violations and follows container processes with container, pod, and namespace identities. Integrations include OpenTelemetry, Prometheus, Kafka, Grafana, ELK dashboards, a GitHub Action, and a Rancher UI extension. Documentation also provides hardening guidance mapped to MITRE, STIG, and CIS practices.
Pricing
KubeArmor: free. This is an open-source runtime security project with no paid tier or hosted subscription described. The price is compelling for organizations able to supply Linux and Kubernetes operations themselves, but it does not include a commercial support contract, managed control plane, or turnkey policy service.
Platforms
KubeArmor runs on API, Linux, and self-hosted deployments. Its matrix covers Kubernetes environments such as GKE, AKS, OKE, IKS, EKS, OpenShift, Rancher, DigitalOcean, and Alibaba Cloud, alongside non-Kubernetes containers, virtual machines, and bare metal. Actual enforcement varies by operating system, CPU architecture, and selected mode, so validate the exact combination before standardizing.
Who it's for
KubeArmor is a strong fit for platform, DevOps, and security teams that operate Linux infrastructure and need policies attached to Kubernetes workload identity. It is also relevant to teams hardening edge, IoT, or 5G workloads across mixed deployment types. It is less suitable when you want a vendor-managed service, a graphical policy workflow as the primary experience, or preventive syscall controls.
Pros and cons
- Pros: open-source and free to run; supports Kubernetes plus containers, VMs, and bare metal; granular allow, audit, and block controls for process, file, network, capability, and resource behavior; workload identity and eBPF telemetry make violations easier to attribute; integrations and MITRE, STIG, and CIS guidance help fit existing security operations.
- Cons: support and enforcement differ by OS, architecture, and mode; some listed environments are observability-only and VMware Tanzu support is still under construction; syscall monitoring cannot block calls; self-hosting leaves deployment, policy maintenance, and ongoing operations to your team.
Alternatives
Fairwinds Polaris is another free open-source option, aimed at small teams and available across Linux, macOS, Windows, web, and self-hosted deployments. Choose it when broad platform access and a small-team policy engine matter more than KubeArmor's runtime enforcement scope.
Pick it when cloud configuration scanning is a better match than self-hosted workload runtime controls.
Kubescape is free, Apache 2.0 software with a CLI and Kubernetes operator. It is the alternative to consider when that operator-and-CLI model fits your Kubernetes workflow.
Monokle is a free, MIT-licensed open-source desktop application. Choose it when a desktop-oriented Kubernetes tool is preferable.
Kyverno is a free Apache 2.0 open-source project for teams seeking that policy framework.
KSPM Pro has a free plan for one Kubernetes cluster with real-time scans and CIS coverage; choose it when that defined hosted scope is enough.
ARMO Platform is a paid, web and self-hosted product with a free trial; consider it when you want a commercial platform around Kubescape.
Falco is a free, open-source Linux runtime option when zero-cost starting and event detection are the priority.
For broader comparisons, see Kubernetes Security Software, Cloud Workload Protection Platforms, and Container Security Software.
Verdict
Choose KubeArmor if you need free, self-hosted runtime enforcement tied to Kubernetes and Linux workload identities, with coverage that extends beyond Kubernetes. Look elsewhere if your environment falls into an observability-only or unfinished matrix entry, if you require blocked system calls, or if your team cannot own the operational work of an open-source security control.
The verdict
KubeArmor provides workload runtime controls across several deployment types, with policy enforcement depending on the environment and mode. Check the support matrix for the operating system, architecture, and enforcement mode in use.
What the maker publishes
- Cloud integrations
- The support matrix lists Kubernetes environments including GKE, AKS, OKE, IKS, EKS, OpenShift, and DigitalOcean Kubernetes. source
- Community support
- Project-level questions can be directed to the maintainer group by email, and the project provides Slack, GitHub Discussions, and GitHub Issues channels. source
- Deployment
- The support matrix documents Kubernetes, non-Kubernetes container, virtual-machine, and bare-metal workload deployments. source
- Deployment options
- The support matrix covers Kubernetes workloads, non-Kubernetes containers, virtual machines, and bare-metal hosts. source
- Enforcement
- It uses Linux Security Modules including AppArmor, SELinux, and BPF-LSM, with eBPF for alerts and telemetry carrying container, pod, and namespace identities. source
- Founded
- 2020 source
- Hardening guidance
- The project documentation describes hardening infrastructure with rules based on MITRE, STIGs, and CIS. source
- Installation
- The getting-started guide installs KubeArmor on a Kubernetes cluster using Helm and kubectl. source
- Install method
- The official site provides Helm commands to add the KubeArmor chart repository and install the KubeArmor Operator. source
- Integrations
- Project repositories include OpenTelemetry, Prometheus, Kafka, Grafana, ELK dashboards, a GitHub Action, and a Rancher UI extension. source
- Intended use
- The project describes use for hardening cloud containers, IoT and edge workloads, and 5G networks. source
- Kubernetes policies
- Policy development can use Kubernetes metadata, and KubeArmor enforces policies based on container or workload identities. source
- Logging
- It records policy violations and tracks container processes using eBPF. source
- Platform support
- The matrix lists Kubernetes environments including GKE, AKS, OKE, IKS, EKS, OpenShift, Rancher, DigitalOcean, Alibaba Cloud, and others, with support depending on OS, architecture, and enforcement mode. source
- Policy actions
- Container policies support Allow, Audit, and Block actions, with Block as the default; system-call monitoring supports audit only. source
- Policy enforcement
- It uses Linux Security Modules such as AppArmor, SELinux, and BPF-LSM to enforce policies at runtime. source
- Policy scope
- Policies can match process paths and directories, file paths and directories, network protocols, capabilities, and system calls. source
- Policy targeting
- Kubernetes workload policies can select pods using labels and label expressions. source
- Project status
- KubeArmor is a community-governed open-source project and a CNCF Sandbox project. source
- Purpose
- KubeArmor is an open-source, cloud-native runtime security system that hardens workloads and enforces security policies. source
- Security reporting
- The project asks users to report security vulnerabilities through its security process rather than as public GitHub issues. source
- Support
- Project-level questions can be directed to the maintainer group by email, CNCF Slack, GitHub Discussions, or GitHub Issues. source
- Support limits
- The support matrix marks some environments as observability-only, including RHEL or CentOS 8.4 and earlier on Kubernetes and Oracle Ampere; VMware Tanzu entries are marked as under construction. source
- What it does
- KubeArmor is a cloud-native runtime security enforcement system that restricts process execution, file access, and networking operations for pods, containers, and nodes. source
Checked against the maker's pages on 9 Oct 2026.