API Deprecation Checker

How to use it

1. Paste one or more manifests into the field. Multi-document YAML works as-is — keep the --- separators and the checker reads each document on its own. Press / to focus the field.
2. Pick the target version: the release your cluster runs today, or the one you are upgrading to. The verdict is computed against that exact version, so 1.24 and 1.25 can answer differently.
3. Read the findings. Removed means the target's API server no longer serves that apiVersion; Deprecated means it still works there but has a named removal release; each row shows the replacement to copy and the field changes to expect.
4. Fix the manifests and paste again, or jump to the per-version tables below — every removal wave since v1.16 has its own anchored table with per-row links into the official guide.

An upgrade note says your cluster's next version stops serving old APIs, and your manifests are where the old apiVersions hide. Paste them here, pick the Kubernetes version you run or plan to reach, and every deprecated or removed apiVersion is flagged with its exact replacement and migration note — checked against the official deprecation guide's full removal history, entirely in your browser. The tables below hold every wave, v1.16 to v1.32.

Examples

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: web

extensions/v1beta1 Ingress is no longer served at v1.22 — removed in v1.22. Migrate to networking.k8s.io/v1, served since v1.19 — spec.backend becomes spec.defaultBackend, backend serviceName/servicePort become service.name and service.port.name or service.port.number, and each path needs a pathType.

apiVersion: batch/v1beta1
kind: CronJob
metadata:
  name: nightly

batch/v1beta1 CronJob is no longer served at v1.25 — removed in v1.25. Migrate to batch/v1, served since v1.21.

apiVersion: autoscaling/v2beta1
kind: HorizontalPodAutoscaler
metadata:
  name: api

autoscaling/v2beta1 HorizontalPodAutoscaler is deprecated since v1.22 but still served at v1.24; it stops being served in v1.25. Migrate to autoscaling/v2, served since v1.23.

apiVersion: apps/v1
kind: Deployment
metadata:
  name: web

apps/v1 Deployment matches no removal row — apps/v1 is a migration target the guide names as served.

Every example on this page is executed against the same engine that powers the tool, on every build.

Common errors

extensions/v1beta1 Ingress is no longer served at v1.22 — removed in v1.22. Migrate to networking.k8s.io/v1, served since v1.19 — spec.backend becomes spec.defaultBackend, backend serviceName/servicePort become service.name and service.port.name or service.port.number, and each path needs a pathType.

KD_REMOVED, the error state: the target version's API server refuses this apiVersion, and the sentence carries the replacement plus the field moves.

autoscaling/v2beta1 HorizontalPodAutoscaler is deprecated since v1.22 but still served at v1.24; it stops being served in v1.25. Migrate to autoscaling/v2, served since v1.23.

KD_DEPRECATED, the warning state: still served at your target, with the removal release named so the migration can be scheduled.

example.com/v1 Widget is not in the curated pack — this pack covers the 24 deprecated or removed API versions on the official guide's removal history (v1.16–v1.32); CRDs and other groups are outside its scope.

KD_UNKNOWN_API, the honest boundary: CRDs and groups outside the guide's history get a named out-of-scope answer, never a false clean.

Nothing to check — paste at least one Kubernetes manifest.

KD_NO_DOCUMENTS: an empty or comment-only paste has nothing to classify, so the checker asks for a manifest instead of showing an empty pass.

Document 1 has no apiVersion field — nothing to check against the pack.

KD_MISSING_APIVERSION: deprecation is a property of the apiVersion string, so a document without one is reported as not checkable rather than silently skipped.

Keyboard shortcuts

/

Focus the manifest field