Kubernetes Manifest Inspector & Linter
Lint Kubernetes YAML for schema, API, security and selector issues
Manifest
0 Bytes of 1 MB · multi-document YAML, JSON and kind: List
Findings
Output
Related Tools
What it checks
Paste or upload Kubernetes YAML or JSON with one or many documents, including kind: List. Each built-in resource is validated against the bundled Kubernetes JSON Schema for its apiVersion and kind, then checked for removed or deprecated APIs, images without a pinned tag, missing or invalid resource requests and limits, privileged containers, privilege escalation, root users, host namespaces, dangerous capabilities, hostPath volumes, missing probes and single replicas.
Cross-resource checks
The inspector compares resources in the same manifest: Service selectors that match no workload, targetPort values that no selected container exposes, Deployment selectors that do not match their pod template, duplicate kind, namespace and name combinations, and autoscalers, disruption budgets or Ingress backends that point to resources missing from the manifest. References to resources defined elsewhere are reported as info, not errors.
Privacy and Secrets
Parsing, schema validation and every rule run in a Web Worker in your browser. The manifest is not uploaded, stored or added to the URL. Secret data and stringData values are masked in the normalized and JSON views and never appear in findings.
Limits
This is a static inspector, not a cluster dry run: admission controllers, quotas, existing objects and custom resource schemas are not checked. Custom resources get structural checks only. Comments and anchors are not kept in the normalized view. Inputs are limited to 1 MB and 300 resources.
