Kubernetes manifest YAML lint

Validators and utilities that complement Kubernetes manifest YAML lint — same session, no sign-up.

YAML-parse manifests and flag missing apiVersion/kind/metadata or odd shapes; walks list roots element-wise. Not kubeconform, CRDs, or cluster admission.

YAML-parse a manifest and check common fields (apiVersion, kind, metadata). Lists of resources are walked element-wise.

How to use this tool

  1. Paste your sample in the input (or fetch from URL if this tool supports it).
  2. Run the main action on the page to execute Kubernetes manifest YAML lint.
  3. Read the result, fix the source data or config, and re-run if needed.

What this check helps you catch

  • YAML-parse manifests and flag missing apiVersion/kind/metadata or odd shapes; walks list roots element-wise. Not kubeconform, CRDs, or cluster admission.
  • Limits called out in the description (what this tool does not verify — e.g. live network reachability, issuer databases, or strict schema contracts unless stated).
  • Structural or syntax mistakes that would break parsers, serializers, or the next step in your workflow.

FAQ

What does Kubernetes manifest YAML lint do?
YAML-parse manifests and flag missing apiVersion/kind/metadata or odd shapes; walks list roots element-wise. Not kubeconform, CRDs, or cluster admission. Use the form above, then see “How to use” and “What this check helps you catch” for behavior detail.
Is this a substitute for server-side validation?
No. Use it for manual checks and triage; production systems should still validate and authorize on the server.
Where does processing happen?
Most validators here run in your browser. If a tool calls an API, that is stated on the page. See the site privacy policy for data handling.