kubewarden/adm-controller

Manage admission policies in your Kubernetes cluster with ease

Hosted by Cloud Native Computing Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓Open shareable report →

kubewarden/adm-controller has 200+ stars and 50+ forks on GitHub, is written in Rust, and was last pushed on Oct 17, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on October 15th, 2026
Created on December 4th, 2020
Open Issues & Pull Requests: 138 (+0)
GitHub issues: Enabled
Number of forks: 55
Total Stargazers: 243 (+0)
Total Subscribers: 7 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 47.8 hours
Mean response time: 49.7 days
90th percentile: 81.2 days
Tracked items: 646

Maintainer activity

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

At least 45% of adm-controller's 11 maintainers work at SUSE. 7 say where they work, and 5 of those are SUSE.

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 3% of issues opened in the past year have never received a reply. 34% of open issues come from outside the core team, a mix of external reports and the maintainers' own roadmap. Work labelled "area/documentation" is answered fastest, typically in about 29 hours, while "area/policy-server" waits about 6 weeks. 88% of issues opened in the past year have been closed, leaving a working backlog. Three people close 84% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 121
New in 7 days: 1
Closed in 7 days: 3
Avg open age: 991 days
Stale 30+ days: 117
Stale 90+ days: 115

Recent activity

Opened in 7 days: 1
Closed in 7 days: 3
Comments in 7 days: 1
Events in 7 days: 9

Top labels

  • kind/epic (67)
  • area/ci (44)
  • area/policy (28)
  • kind/good first issue (25)
  • area/policy-evaluator (23)
  • area/kwctl (21)
  • area/community (19)
  • area/policy-server (18)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Kubewarden Admission Controller is a Kubernetes Dynamic Admission Controller that uses policies written in WebAssembly to manage admission control in your cluster.

The tool solves the problem of managing admission policies across Kubernetes clusters by providing a unified system that dynamically registers policies and reconciles them with the cluster's webhook infrastructure. It works by running policies compiled to WebAssembly, which are evaluated by a policy server component at admission time. This approach allows policies to be written in multiple languages that compile to WebAssembly, including those using CEL and Rego syntax compatible with existing policy frameworks.

Teams should adopt this tool if they need flexible, language-agnostic admission control without being locked into a single policy language. It suits organizations already familiar with policy-as-code approaches through Open Policy Agent or Gatekeeper, as it provides similar capabilities through a WebAssembly-based runtime. The project includes an audit scanner component for validating existing cluster resources against registered policies, and a CLI tool for testing policies before deployment. Namespaced policies can be restricted to target only approved resource types, providing security boundaries for multi-tenant clusters. The unified Helm chart consolidates what were previously three separate charts, simplifying deployment and lifecycle management.

The project maintains active development with regular updates to its core components. The codebase is written primarily in Rust, indicating a focus on performance and safety in the admission controller runtime. Documentation is comprehensive and centralized, with dedicated guides for each component and migration paths for users transitioning from legacy deployment approaches. The project provides clear configuration options for default policy servers and recommended policies, with explicit controls over which resources namespaced policies can target.