instrumenta/kubeval

Validate your Kubernetes configuration files, supports multiple Kubernetes versions

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

instrumenta/kubeval has 3k+ stars and 200+ forks on GitHub, is written in Go, and was last pushed on Jan 29, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 32 minutes ago
Added to GitGenius on September 21st, 2026
Created on June 25th, 2017
Open Issues & Pull Requests: 103 (+0)
GitHub issues: Enabled
Number of forks: 227
Total Stargazers: 3,230 (+0)
Total Subscribers: 27 (+0)

Repository Insights (GitGenius)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 2
New in 7 days: 0
Closed in 7 days: 1
Avg open age: 554 days
Stale 30+ days: 2
Stale 90+ days: 2

Recent activity

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

Top labels

  • question (1)
  • schema (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

kubeval is a command-line tool that validates Kubernetes configuration files against the official Kubernetes schema.

The tool addresses the problem of catching configuration errors before deploying to a cluster. It works by taking YAML or JSON manifests as input and validating them against schema definitions that correspond to specific Kubernetes versions. This allows developers to verify that their configurations conform to the API specifications without needing a running cluster. The tool supports multiple Kubernetes versions, enabling validation against the schema appropriate for the target deployment environment.

kubeval suits developers and operators who want to catch misconfigurations early in their workflow, whether in local development, CI/CD pipelines, or pre-deployment checks. It is particularly useful for teams managing configurations across multiple Kubernetes versions or those seeking to enforce configuration standards before resources reach a cluster. The tool's schema-based approach makes it suitable for both simple validation tasks and integration into automated workflows.

The project shows consistent maintenance with regular updates addressing bug fixes and schema updates. Development activity demonstrates responsiveness to issues and pull requests, with fixes being merged and released in a timely manner. The project maintains active engagement with its user base through issue tracking and documentation updates.