All Tools View Categories About Contact Privacy

API Version Deprecation Checker

Flag deprecated or removed apiVersions against a target Kubernetes version.

Runs entirely in your browser - nothing is uploaded and no cluster connection is made.
Your report will appear here.

About API Version Deprecation Checker

The API Version Deprecation Checker reads the apiVersion of each manifest you paste and compares it to a target Kubernetes version. It flags apiVersions that were deprecated or removed so you can fix them before an upgrade breaks your workloads.

Pick the Kubernetes version you plan to run, paste one or more manifests, and the tool reports each problem with a recommended replacement.

Nothing is uploaded. The analysis runs entirely in your browser.

Features

  • Target aware - choose the Kubernetes version you run.
  • Removed vs deprecated - clear severity.
  • Common removals - apps, extensions, networking, batch, policy, autoscaling and more.
  • Multi-doc - check several manifests at once.
  • Copy / Download / Print - export the report.

How to Use

  1. Pick the target Kubernetes version.
  2. Paste your manifest(s).
  3. Click Check.
  4. Fix any REMOVED apiVersions before upgrading.

Examples

Example 1 - Ingress. networking.k8s.io/v1beta1 is removed in 1.22; use v1.

Example 2 - Deployment. apps/v1beta1 is removed in 1.16; use apps/v1.

Example 3 - CronJob. batch/v1beta1 is removed in 1.25; use batch/v1.

Benefits

  • Upgrade safety - catch removals before they break.
  • Clear guidance - suggested replacement per version.
  • Private - runs fully in the browser.
  • Exportable - copy, download or print.

Frequently Asked Questions

What does this checker do?
It inspects the apiVersion of every manifest you paste and tells you whether that version was deprecated or removed in the Kubernetes version you target.
Which versions are covered?
Common removed versions such as apps/v1beta1, apps/v1beta2, extensions/v1beta1, networking.k8s.io/v1beta1, batch/v1beta1, policy/v1beta1 and autoscaling/v2beta1/v2beta2.
How is the target version used?
If a version was removed on or before your target, it is reported as REMOVED (the manifest will not apply). Otherwise it is reported as deprecated.
Does this connect to a cluster?
No. Paste your YAML; everything is analysed in your browser.
What should I do with flagged versions?
Update the apiVersion to the suggested supported version and adjust the schema where needed before upgrading the cluster.