No. It is parsed for this response and then discarded. Do not rely on that as a place to put secrets.

Does this apply the manifest to a cluster?

No. Nothing is sent to Kubernetes. There is no kubeconfig field.

Will it catch every misconfiguration?

No. It flags a short list of mistakes we see in reviews. It is not a policy engine.

Tools · Mail, DNS and sites

Kubernetes YAML linter

Paste a manifest. We flag missing resource limits, a latest image tag, a privileged container, and a long-running workload with no probes. The manifest is checked and then discarded.

The manifest is checked and then discarded. Do not paste secrets. This page does not keep a copy.

How to use it

Paste one manifest or several documents separated by a line of three dashes.
Fix high-severity lines first: privileged, latest tags, and missing limits.
Jobs are not expected to have liveness probes. Deployments and similar workloads are.

Questions

Is the YAML stored?: No. It is parsed for this response and then discarded. Do not rely on that as a place to put secrets.
Does this apply the manifest to a cluster?: No. Nothing is sent to Kubernetes. There is no kubeconfig field.
Will it catch every misconfiguration?: No. It flags a short list of mistakes we see in reviews. It is not a policy engine.

An automated client can POST JSON to /api/tools/kubernetes-lint with yaml. The OpenAPI document is at /api/tools, with a short guide at /llms.txt. Nothing submitted is stored.