API Deprecation Checker
Paste your Kubernetes YAML manifests to detect deprecated and removed APIs before upgrading.
Data sources: endoflife.date (Kubernetes and cloud provider version lifecycles), GitHub (Official Kubernetes release changelogs), NIST NVD (National Vulnerability Database for CVE data), Pluto by Fairwinds (API deprecation detection rules), Artifact Hub (Helm chart metadata and compatibility)
Frequently Asked Questions
- What Kubernetes versions does the Deprecation Checker support?
- The checker covers Kubernetes versions 1.18 through 1.32, detecting APIs deprecated or removed in any of these versions.
- Can I check multiple YAML documents at once?
- Yes. The checker supports multi-document YAML files separated by ---. Each document is analyzed independently.
- Where does the deprecation data come from?
- Deprecation data is sourced from Pluto by Fairwinds, an open-source tool that tracks Kubernetes API deprecations and removals.
Related Tools
View all tools →Upgrade Planner
Plan your Kubernetes upgrade path with risk scores, breaking changes, and CVE impact.
Cloud Version Matrix
Compare EKS, GKE, AKS, and OKE Kubernetes version support and EOL dates.
CVE Dashboard
Track security vulnerabilities for top Kubernetes ecosystem container images.
Helm Compatibility Checker
Check if a Helm chart is compatible with your target Kubernetes version.