Kubernetes manifest validator
About Kubernetes Manifest Validator
The Kubernetes manifest validator checks YAML before it reaches a cluster. It covers YAML syntax, resource basics, stable built-in API versions and common workload mistakes.
How it works
YAML and resource basics
Multi-document YAML 1.2 files and List resources are split into individual objects. Each resource must have apiVersion, kind, metadata and a non-empty name.
Built-in resource checks
Pods, Deployments and other workloads, Jobs, CronJobs, Services, ConfigMaps, Secrets and RBAC resources get targeted checks. These cover required fields, stable API versions, containers, selectors, base64 data and string maps.
Operational warnings
The report flags mutable image tags, privileged containers and missing resource requests or limits. Each message names the document, the resource and the escaped object path.
Frequently asked questions
Is this the same as kubectl apply --dry-run=server?
No. Only the API server can apply your cluster's full OpenAPI, admission, CRD and policy rules. Use this for a quick local check, then run a server-side dry run.
Are custom resources validated?
Only their apiVersion, kind and metadata. They are reported as unbundled, because their CRD schema lives in your cluster.
Does the validator contact a cluster?
No. All checks run in your browser. It never reads credentials or kubeconfig files.
Sources & last verified
We checked this tool's behavior and the claims on this page against the specifications below on . The tool runs in your browser, so the output you see is exactly what the engine produced.
Found a wrong result or an outdated claim? Report an error and we will check it again.
YAML Validator / Linter
JSON Validator
JSON Diff / Compare
JSON Schema Generator
JSON Schema Validator
JWT Decoder