Validate Kubernetes YAML — Structural Checks
Validate Kubernetes manifests with structural browser checks: apiVersion, kind, metadata, and kind-specific rules for common resources. Not kubeconform, kubectl dry-run, or full OpenAPI schema validation against a cluster.
Developer notes
• Parses with js-yaml loadAll; validates structure in the browser. • Checks shared fields (apiVersion, kind, metadata.name) plus kind-specific rules for a curated subset. • Not kubeconform, kubectl --dry-run, or OpenAPI schema from an apiserver. • Debounced while typing. • Max input 512 KB.
When teams pick this route
• Spot a missing selector or container list on a pasted Deployment. • Sanity-check multi-doc YAML from kubectl get before sharing. • Teach manifest shape with immediate feedback. • Pair with format Kubernetes after fixing issues.
Worked examples
Valid Deployment skeleton
Input
Validation result
Missing metadata.name
Input
Validation result
Navigate related Kubernetes tools
Pretty-print with format Kubernetes, scaffold resources via generate Deployment, or browse the Kubernetes hub.
Kubernetes validator FAQ
Structural scope only
Is this kubeconform or kubectl dry-run?
No. Checks are structural and kind-aware for a subset of fields in the browser. They do not load Kubernetes OpenAPI schemas or contact a cluster.
Does a valid result mean the manifest will apply?
No. Structural OK does not guarantee admission, RBAC, image pull, or API version availability on your cluster.
Are CRDs fully validated?
Custom resources get shared-field checks only unless a kind-specific rule exists. Treat CRDs carefully.
Multi-document files?
Yes — each non-null document is checked; issues can name the document index and line when available.
More Kubernetes tools in this cluster
Looking for converters, encoders, formatters, and minifiers in one place? Developer tools hub Open the curated developer tools catalogue.