kyverno/kyverno-authz

Kyverno policies based authorization ❤️

Hosted by Cloud Native Computing Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓

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

Summary Information

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

Repository Insights (GitGenius)

Median issue/PR response: 4.5 days
Mean response time: 15.8 days
90th percentile: 19.7 days
Tracked items: 15

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 7
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 197 days
Stale 30+ days: 7
Stale 90+ days: 5

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 (11)
  • question (2)
  • bug (1)
  • github_actions (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Kyverno-authz is an authorization service that enforces Kyverno policies for Envoy proxies and plain HTTP services.

The tool solves the problem of applying fine-grained authorization policies across distributed systems by leveraging Kyverno's policy engine. It operates in two modes: it integrates with Envoy's External Authorization filter to make authorization decisions in service mesh and API gateway deployments, or it functions as a standalone HTTP authorization server that any HTTP service can query for allow or deny decisions based on Kyverno policies.

Organizations should consider this tool if they already use Kyverno for policy management and want to extend those same policies to control access at the API and service level. It suits service mesh architectures, API gateway deployments, and scenarios where you need consistent authorization logic across multiple HTTP services. The tool is in development stage, which means its API and behavior may change.

The project maintains a roadmap documenting planned features and upcoming updates. The maintainers actively solicit contributions through a good first issues list and encourage community involvement via the Kyverno Slack channel and community page. Documentation is provided for both Kubernetes and local installation scenarios, with a quick start guide available to help new users get running.