kyverno/chainsaw

Declarative K8s e2e testing

Hosted by Cloud Native Computing Foundation · part of Linux Foundation

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

kyverno/chainsaw has 600+ stars and 90+ forks on GitHub, is written in Go, and was last pushed on Sep 3, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 50 minutes ago
Added to GitGenius on October 15th, 2026
Created on October 10th, 2023
Open Issues & Pull Requests: 74 (+0)
GitHub issues: Enabled
Number of forks: 99
Total Stargazers: 623 (+0)
Total Subscribers: 7 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 26.9 days
Mean response time: 85.7 days
90th percentile: 277.7 days
Tracked items: 80

How this project is maintained

97% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "question" is answered fastest, typically in about 28 hours, while "enhancement" waits about 5 weeks. Three people close 82% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 33
New in 7 days: 0
Closed in 7 days: 1
Avg open age: 453 days
Stale 30+ days: 32
Stale 90+ days: 28

Recent activity

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

Top labels

  • enhancement (38)
  • bug (32)
  • question (12)
  • Contribfest (8)
  • documentation (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Chainsaw is a declarative testing tool for Kubernetes operators and controllers.

Chainsaw addresses the challenge of writing end-to-end tests for Kubernetes workloads by providing a declarative approach rather than imperative test code. Instead of writing traditional test scripts, users define test scenarios in a declarative format that specifies the desired state, actions to perform, and assertions to validate. This approach makes tests more readable, maintainable, and easier to reason about, particularly for complex Kubernetes environments where multiple resources interact.

Teams building Kubernetes operators and controllers should consider Chainsaw if they want tests that are easier to write and understand compared to traditional programmatic testing frameworks. The tool works well for projects that need to validate operator behavior across multiple Kubernetes resources and their interactions. While Chainsaw was initially developed for testing Kyverno policies, it can declaratively test any Kubernetes objects, making it applicable beyond its original use case.

The project maintains active community engagement through weekly public meetings held on Thursdays, with an open agenda where community members can raise topics and provide feedback. The maintainers actively solicit input from users and contributors through these structured forums. Documentation is comprehensive, with multiple blog posts and video resources explaining core concepts like assertion trees and practical testing patterns. The project publishes a roadmap outlining planned features and upcoming updates, signaling transparency about the direction of development.