Kubernetes Yaml Validator — 100% Client-Side Private Tool

Kubernetes v1.20 - v1.32+OpenAPI Schema GuardRFC 1123 DNS Compliance

Validate Deployment, Service & Ingress YAML Before `kubectl apply`

Catch subtle YAML indentation errors, forbidden tab characters, deprecated API versions, selector label mismatches, and multi-port naming violations directly inside your browser. No manifest data or tokens are transmitted to any server.

Manifest Health

100/100

A+

manifest.yaml94 lines

Syntax OK

apiVersion: apps/v1
kind: Deployment
metadata:
  name: web-api-deployment
  namespace: production
  labels:
    app.kubernetes.io/name: web-api
    app.kubernetes.io/instance: prod-web-api
    app: web-api
spec:
  replicas: 3
  selector:
    matchLabels:
      app: web-api
  template:
    metadata:
      labels:
        app.kubernetes.io/name: web-api
        app: web-api
    spec:
      containers:
      - name: web-api
        image: registry.example.com/api/server:v2.4.1
        ports:
        - containerPort: 8080
          name: http-api
          protocol: TCP
        resources:
          limits:
            cpu: 500m
            memory: 512Mi
          requests:
            cpu: 100m
            memory: 128Mi
        readinessProbe:
          httpGet:
            path: /healthz
            port: 8080
          initialDelaySeconds: 5
          periodSeconds: 10
        livenessProbe:
          httpGet:
            path: /live
            port: 8080
          initialDelaySeconds: 15
          periodSeconds: 20
        securityContext:
          runAsNonRoot: true
          allowPrivilegeEscalation: false
---
apiVersion: v1
kind: Service
metadata:
  name: web-api-service
  namespace: production
  labels:
    app.kubernetes.io/name: web-api
    app: web-api
spec:
  type: ClusterIP
  selector:
    app: web-api
  ports:
  - port: 80
    targetPort: 8080
    protocol: TCP
    name: http-api
---
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: web-api-ingress
  namespace: production
  annotations:
    nginx.ingress.kubernetes.io/ssl-redirect: "true"
    nginx.ingress.kubernetes.io/proxy-body-size: 16m
spec:
  ingressClassName: nginx
  tls:
  - hosts:
    - api.example.com
    secretName: api-tls-cert
  rules:
  - host: api.example.com
    http:
      paths:
      - path: /
        pathType: Prefix
        backend:
          service:
            name: web-api-service
            port:
              number: 80

Indent: 2 spaces (Tab key supported)

1,957 chars Client-Evaluated

No Issues Detected

Your Kubernetes manifests passed all schema, indentation, and cross-reference checks! Ready for kubectl deployment.

Kubernetes YAML Validation Guide & Common Pitfalls

1. Indentation & Tabs

YAML specifications strictly prohibit tab characters (\t) for indentation. A single tab will cause error: error unmarshaling JSON. Always use 2 standard spaces.

2. Selector Label Mismatch

In apps/v1, every label defined in spec.selector.matchLabels must exist in spec.template.metadata.labels with identical values. Otherwise, the Deployment controller cannot identify Pods.

3. Ingress pathType & Ports

In networking.k8s.io/v1, pathType is required (Exact or Prefix). Legacy serviceName is replaced by nested service: { name, port: { number } }.