Validate Kubernetes YAML

Lint Kubernetes manifests for identity, workload, health, resource, and security omissions.

freeworks offlinenothing uploaded

ToolKubernetes YAML Validator

Input

Output

—

Put this on your own site

The frame below runs the same code as this page, in the reader's own browser. Nothing is sent to us, and nothing is sent to you.

AccentBackground

Pick a dark background and the text and panels follow it, so the frame stays readable on a dark page.

How it works

Manifest text is scanned for apiVersion, kind, metadata, labels, images, resources, probes, security context, and mutable tags. The report is advisory and does not contact an API server or run OpenAPI validation.

Checks target common workload fields.
Warnings remain advisory because custom resources differ.

Worked example

Deployment missing probes + resource limits

Validate a Deployment that uses :latest tag and lacks labels, resource limits, and health probes

Input

											apiVersion: apps/v1
kind: Deployment
metadata:
  name: web
spec:
  template:
    spec:
      containers:
        - name: web
          image: nginx:latest

Output

												# Kubernetes Manifest Validation

Kind: Deployment
Errors: 0 | Warnings: 5

## Warnings
  - Line 10: Avoid using ':latest' image tag
  - No labels defined - labels are recommended for organization
  - No resource requests/limits defined - recommended for production
  - No livenessProbe defined - recommended for reliability
  - No readinessProbe defined - recommended for zero-downtime deploys

## Info
  - No namespace specified - will use 'default'
  - No securityContext defined - consider adding for security hardening

Manifest structure is valid!

When to use this

CI gates, platform reviews, and security checks lint manifests before apply.

Edge cases

A custom resource can be valid without built-in workload fields.
A present resource request can still be too small.
A non-latest tag can remain mutable under registry policy.

References

Kubernetes objects