kubewarden/runtime-enforcer

A runtime enforcement solution for your Kubernetes cluster

Hosted by Cloud Native Computing Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓

kubewarden/runtime-enforcer has 10+ stars and 10+ forks on GitHub, is written in Go, and was last pushed on Oct 17, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 12 minutes ago
Added to GitGenius on October 15th, 2026
Created on November 10th, 2025
Open Issues & Pull Requests: 34 (+0)
GitHub issues: Enabled
Number of forks: 10
Total Stargazers: 10 (+0)
Total Subscribers: 4 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 18.6 hours
Mean response time: 13.8 days
90th percentile: 49.1 days
Tracked items: 204

Maintainer activity

6 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 18, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

About 6% of issues opened in the past year have never received a reply. Only 21% of open issues come from outside the core team — the tracker reads mainly as internal planning. Work labelled "bug" is answered fastest, typically in under an hour, while "tech-debt" waits about 6 days. 87% of issues opened in the past year have been closed, leaving a working backlog. Three people close 66% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 28
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 158 days
Stale 30+ days: 25
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • enhancement (55)
  • bug (26)
  • documentation (20)
  • tech-debt (11)
  • tetragon-workstream (7)
  • P1 (5)
  • wontfix (4)
  • EPIC (3)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Kubewarden Runtime Enforcer is a Kubernetes security tool that enforces process execution policies at the kernel level using eBPF.

The tool addresses the challenge of controlling which processes can run inside Kubernetes workloads by observing and restricting process execution through kernel-level enforcement. It operates in three distinct phases: Learn mode observes process executions and generates policy proposals per workload; Monitor mode reports policy violations without blocking them; Protect mode actively blocks executions that violate the approved allow-list. This phased approach lets operators understand workload behavior before enforcing restrictions.

Adoption requires Kubernetes 1.31 or later with containerd or CRI-O runtime configured with NRI enabled, plus specific kernel and architecture compatibility. The tool is deployed via Helm chart and depends on cert-manager and cert-manager-csi-driver. It includes a bundled OpenTelemetry collector for violation metrics and events, eliminating the need for external observability infrastructure in basic setups. The project is in Beta, so users should review the design documents and compatibility matrix before deployment. This approach suits teams seeking kernel-level process enforcement without external policy engines, particularly those already invested in the Kubewarden ecosystem.

Development activity shows consistent engagement with the project. The team maintains comprehensive documentation including quick-start guides, compatibility matrices, and detailed phase explanations. Configuration is exposed through a well-structured Helm values file with clear separation of concerns across controller, agent, debugger, learning, telemetry, and scheduling components. The project preserves CRD lifecycle through Helm annotations, indicating attention to operational concerns around upgrades and resource management.