Kubernetes Manifest Validator
About Kubernetes Manifest Validator
Kubernetes Manifest Validator provides a private preflight check for YAML syntax, resource envelopes, stable built-in API versions and common workload mistakes before a manifest reaches a cluster.
How it works
YAML and resource envelopes
Multi-document YAML 1.2 streams and List resources are expanded into individual objects. Every resource is checked for apiVersion, kind, metadata and a non-empty name.
Built-in structural checks
Common Pods, workloads, Jobs, CronJobs, Services, ConfigMaps, Secrets and RBAC resources receive targeted required-field, stable API, container, selector, base64 and string-map checks.
Operational warnings
The report calls out mutable image tags, privileged containers and missing resource requests or limits. Diagnostics identify the document, resource and escaped object path.
Frequently asked questions
Is this equivalent to kubectl apply --dry-run=server?
No. Only the API server can apply the cluster's complete OpenAPI, admission, CRD and policy rules. Use this as a fast local preflight, then run server-side dry-run for authoritative validation.
Are custom resources validated?
Their Kubernetes envelope is checked and they are reported as unbundled. Their CRD schema is not available unless connected to a specific cluster.
Does the validator contact a cluster?
No. It performs bundled structural checks entirely in the browser and never reads credentials or kubeconfig files.
Sources & last verified
The behaviour of this tool and the claims on this page were checked against the specifications below on . Everything 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 it will be re-verified.