Validate multi-document Kubernetes YAML manifests for syntax errors, deprecated apiVersions, `:latest` tags, and missing resource limits—and strip `kubectl get -o yaml` noise in one click.
Validation & Cleaned Output (1 doc)0 err · 2 warn
[Doc 1 · warning]Container "api" uses mutable tag ("ghcr.io/acme/payments:latest"). Pin a specific version or digest.
[Doc 1 · warning]Container "api" has no CPU/memory requests & limits defined.
[Doc 1 · info]Container "api" has no readinessProbe or livenessProbe.
What does this Kubernetes manifest validator check?
It validates multi-document YAML syntax, required top-level fields (`apiVersion`, `kind`, `metadata.name`), deprecated Kubernetes API versions (like `extensions/v1beta1`), mutable `:latest` container image tags, missing CPU/memory requests & limits, health probes, and `securityContext`.
How does the kubectl YAML cleaner prepare manifests for GitOps?
When you export a running object via `kubectl get deploy -o yaml`, Kubernetes injects noisy runtime fields (`status`, `metadata.uid`, `resourceVersion`, `managedFields`, `generation`, `creationTimestamp`). Checking "Strip cluster status / uid / managedFields" removes them automatically.
Are my production Kubernetes manifests uploaded to a server?
Never. All YAML parsing, linting, and cleaning run 100% locally in your browser—safe for internal cluster configs and private GitOps repos.