Kubernetes manifest validator
Validate Kubernetes manifests against the official schema for your selected version. Find unknown fields, incorrect types, removed APIs, selector mismatches, resource quantity mistakes and broken volume mounts before you apply them.
Up to 1,000,000 characters, 100 documents and 5,000 objects. Everything runs on your device in a background worker. Downloads: JSON report, CSV findings and SARIF 2.1.0. Paste one or more manifests. Separate documents with ---. Up to 1,000,000 characters. Review the settings before running.
Your result
How to use Kubernetes manifest validator
- Paste your manifests. Separate documents with ---.
- Choose the Kubernetes version of your cluster.
- Run the check and review each finding with its line.
- Download the JSON report, CSV or SARIF file.
Useful next steps
What is checked
Happytails.ai uses official Kubernetes OpenAPI schemas pinned to baseline releases v1.25.0 through v1.34.0, from the Kubernetes repository under Apache-2.0. Only the version you choose is loaded. Structured fields, required values, nested types and unknown fields are checked, with line numbers and field paths in the report.
Rules in brief
Additional rules check removed APIs, names and labels, selectors that do not match pod templates, duplicate container names, ports and resource quantities, requests above limits, probe handlers and mounts of undefined volumes. The report records the selected schema source and its SHA-256.
Coverage
A schema match checks the bundled structural schema plus the listed semantic rules. Cluster admission policies, feature gates and custom-resource schemas are not available. An unknown apiVersion and kind produces an incomplete-coverage warning. The report never marks it schema-valid. Baseline release schemas may differ from later patches or your live cluster.