Kubernetes
Kubernetes API Deprecation Checker
Enter an apiVersion and kind to check if the API has been deprecated, when it was removed, and what the replacement API version is.
No data is transmitted — everything runs locallyTool
About this tool
Kubernetes API Deprecation Checker
The Kubernetes API Deprecation Checker identifies removed and deprecated API versions, showing removal release, replacement API, and spec changes for common resources.
• Check before a Kubernetes version upgrade whether manifests use removed APIs
• Find the replacement API for a deprecated extensions/v1beta1 resource
• Validate that Helm chart API versions are compatible with a target Kubernetes version
• Debug 'no matches for kind' errors after a cluster upgrade
Next step
Init Container Overhead Calculator — Calculate pod resource requests accounting for init container overhead and sequential startup.
Open Init Container Overhead Calculator →
FAQ
What does this tool tell you?
The Kubernetes API Deprecation Checker identifies removed and deprecated API versions, showing removal release, replacement API, and spec changes for common resources.
What affects the result most?
API version deprecation timeline: Kubernetes deprecates APIs 3 releases before removal. Common deprecations: extensions/v1beta1 Ingress → networking.k8s.io/v1 (removed 1.22), policy/v1beta1 PodSecurityPolicy removed 1.25. batch/v1beta1 CronJob → batch/v1 (removed 1.25).
How should I use the result?
Treat the tool's output as a first-pass check, not a proof of correctness. A clean pass means no issues in the patterns this tool recognizes; a failure points to a specific problem you can investigate in your source. The underlying spec is the authoritative source for edge cases.
Related tools