Kubernetes manifest (multi-document YAML works)

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.27
          ports:
            - containerPort: 80
          resources:
            requests:
              cpu: 50m
              memory: 64Mi
          readinessProbe:
            httpGet:
              path: /
              port: 80
---
apiVersion: v1
kind: Service
metadata:
  name: web
spec:
  selector:
    app: web
  ports:
    - port: 80
      targetPort: 80

2 documents0 errors0 warnings1 info

Deployment/webapps/v1

spec.template.spec.containers[0].livenessProbeNo livenessProbe — crashed containers are only restarted when the process exits.

Service/webv1

Looks good — no issues found.

About Kubernetes YAML Validator

Paste one or more manifests (--- separated) and get per-document checks: envelope rules (apiVersion, kind, metadata.name, DNS-1123 naming), kind-specific requirements for 20+ resource types, and the mistakes that actually bite — selector/template label mismatches, missing service ports, bad CronJob schedules, HPA min>max, non-base64 Secret data, invalid RBAC rules and deprecated apiVersions.

It also flags operational smells: unpinned or :latest images, missing resource requests/limits and absent liveness/readiness probes. This is lint-level validation, not a schema check — for the full contract use kubectl apply --dry-run=server. Everything runs locally in your browser.