DEVELOPER TOOLS

Kubernetes Manifest Linter

Check one or more Kubernetes YAML resources for common structural mistakes and selected deployment-safety issues—without sending a manifest to a cluster.

LOCAL YAML ANALYSIS

Lint Kubernetes manifests

Browser-only · no cluster access

Paste YAML directly. Separate resources with ---. Input limit: 500,000 characters. The linter never runs or applies a manifest.

Show a safe Deployment example
apiVersion: apps/v1
kind: Deployment
metadata:
  name: web
spec:
  replicas: 2
  selector:
    matchLabels:
      app: web
  template:
    metadata:
      labels:
        app: web
    spec:
      containers:
        - name: web
          image: nginx:1.25

Validation scope: This is a deterministic local structural and common-safety check, not full Kubernetes API-server or OpenAPI schema validation. It compares Deployment matchLabels entries with template labels, but does not evaluate matchExpressions operators. It does not contact a cluster, fetch remote schemas, or execute manifests.

No errors found by these checks.

found in resource document(s). Review the messages and validate against your target Kubernetes version before deployment.

Warnings

YAML parsing and checks run in your browser only. Manifests are not uploaded, and the tool has no Kubernetes cluster access.

Kubernetes manifest linter guide

Kubernetes manifests declare resources such as Deployments, Pods, Services, and ConfigMaps. This linter reads one or more YAML documents locally and checks common structural requirements and deployment mistakes before you use a manifest in a cluster.

The report is a practical first pass, not a Kubernetes API server. It does not know which CRDs, admission policies, API versions, or cluster-specific defaults are installed in your environment, so important changes still need validation against the target cluster.

Review each resource and its identity

A typical resource declares an apiVersion, kind, and metadata.name. Multi-document YAML is common for related objects; check each document’s identity and make sure names and namespaces match the references used by other resources.

The linter can call out duplicate resource identities and missing required fields in the structures it recognizes. A warning is not necessarily a deployment failure, and a clean result does not validate every field allowed by every Kubernetes version. Inspect the manifest alongside the API version and resource documentation for your cluster.

Check workload selectors and containers

Deployments and Pods have nested workload specifications. For a Deployment, this checker compares each matchLabels entry with the Pod template labels and accepts a non-empty matchExpressions selector, but it does not evaluate expression operators. Verify replica counts and container definitions too; these relationships are easy to mistype while remaining valid YAML.

Image tags, pull secrets, probes, resource requests, security contexts, volumes, ports, and environment variables have operational consequences. A local linter can highlight common shape problems, but it cannot know whether a registry image exists, whether credentials work, or whether a resource limit fits your production workload.

Use the cluster as the final authority

This page does not make API-server calls, retrieve schemas, apply manifests, or contact a Kubernetes cluster. Custom resources and vendor extensions may be outside the local rules, and a manifest accepted by one cluster can be rejected by another because their installed APIs and admission policies differ.

For a release, validate against the intended Kubernetes version with your normal CI or server-side dry-run workflow. Review access controls and secret handling separately; pasted manifests stay in this browser, but values are still visible on the device where you use the page.

Frequently asked questions

Does this validate against the Kubernetes API server?

No. It runs local structural and common-safety checks, not a server-side schema or admission-policy validation.

Can I paste several manifests at once?

Yes. The linter accepts multi-document YAML so related resources can be reviewed together.

Are custom resources fully checked?

No. CRDs and cluster-specific schemas are not fetched, so their fields need validation with the schema or tooling for your cluster.

Does it apply or upload my manifest?

No. The YAML is parsed locally and is never applied to a cluster or sent to a server.

Privacy note: this tool processes your data in your browser. Your inputs and files are not submitted to NAB Tools.