K8s Deprecation Checker
Paste your Kubernetes YAML manifests. Get auto-fixed versions, upgrade path timeline, and deprecation warnings for your target K8s version. Better than kubent + Pluto combined.
Supports multi-document YAML (--- separated)
How It Works
Set Your Path
Choose your current K8s version and target version. The checker analyzes the upgrade path and shows what breaks at each step.
Paste & Analyze
Paste your YAML manifests. Each resource is checked against 99 deprecation rules covering K8s core, cert-manager, and Istio APIs.
Get Auto-Fixed YAML
Download corrected YAML with updated apiVersions and migrated fields. Preserve comments and formatting.
FAQ
Is my YAML sent anywhere?
No, everything is processed locally in your browser. Your YAML never leaves your device. We only load the js-yaml parser from a CDN to handle multi-document parsing.
How does auto-fix work?
We perform text-based replacements on your raw YAML to preserve formatting and comments. apiVersion fields are updated, and Ingress specs are migrated (serviceName→service.name, servicePort→service.port.number, kubernetes.io/ingress.class→spec.ingressClassName).
What versions are covered?
Kubernetes 1.6 through 1.35, plus cert-manager and Istio deprecations. We track 99 deprecation rules including the major removals in 1.16, 1.22, 1.25, 1.26, 1.29, and 1.32.
Can I use this in CI?
npx releaserun k8s-check (coming soon). For now, use this web tool to validate your manifests before applying them to your cluster.
Why not just use kubent/Pluto?
We auto-fix your YAML and show the full upgrade path timeline. Use both! kubent scans live clusters, Pluto checks Helm charts, and we handle static YAML with auto-correction.
Stay ahead of Kubernetes deprecations
Track K8s releases, API deprecation timelines, and get migration guides when new versions land.