k8s-yaml-validator

Validate Kubernetes YAML manifests by checking syntax and schema errors before cluster deployment. This process detects indentation, type, and required-field issues across Deployments, Services, and CRDs to prevent deployment failures.

Linting multi-document Kubernetes YAML resources works by parsing each document independently to verify resource structure and required fields. It uses yamllint and kubeconform to perform static checks across all bundled manifests.

You can validate Custom Resource Definitions without a cluster by using CRD documentation lookup and detection scripts. This offline validation provides guidance to prevent schema violations in Custom Resources without needing server-side access.

You need kubectl to run server-side dry-run validation because an accessible cluster is required. This method validates admission controllers and policies by simulating the deployment of your manifests against the live cluster state.

The best way to check Kubernetes YAML syntax and schema errors locally is using kubeconform and yamllint. These tools perform static validation on your manifests to catch indentation, type, and required-field errors before deployment.

A limitation of static Kubernetes manifest validation is that it cannot evaluate admission controllers or dynamic cluster policies. You must use server-side dry-run validation with an accessible cluster to catch these runtime deployment errors.