Why aren't objects already in the cluster a problem?

The API server converts them. What breaks is whatever still writes or reads a removed version, so that is what the check looks for.

Which versions does it cover?

The version you pick, the next by default, plus the versions removed in the two releases after it.

The check is free; converted manifests and rewriting a release's stored manifest are part of Pro, free for 14 days, no card.

Kubernetes upgrade check

Know what breaks before you upgrade Kubernetes

Pick the next minor version and KubeDrive lists everything that still writes or reads an API version the new release no longer serves. It reads and changes nothing.

Download for macOS

brew install --cask aleksskoz/tap/kubedrive

macOS 13 or later · Apple silicon and Intel · signed and notarized by Apple

Download for Windowsx64 · Arm64

Windows 10 1809 or later, Windows 11 · not code-signed yet: More info → Run anyway

Download .deb Download .rpmArm64: .deb · .rpm

sudo apt install ./kubedrive_0.6.7_amd64.deb

Debian 13, Ubuntu 24.04, Fedora 40 and newer · GTK 4 and WebKitGTK 6.0 come as dependencies

Free forever for two clusters · Pro free for 14 days, no card

Helm releases

Whose stored manifest names a removed version: after the cluster upgrade their upgrade and rollback fail with "unable to build kubernetes objects from current release manifest".

Manifests applied with kubectl

Found from last-applied-configuration: the next kubectl apply of the same file would fail.

Clients still calling removed versions

An old controller, operator or CI job, from the API server's own request counts.

Removed kinds and old nodes

Kinds with no successor, such as PodSecurityPolicy, and kubelets too old for the new control plane.

Converted manifestsPro

Each finding shown rewritten for the new version, the moved fields marked, ready to copy into its repository.

Fix a release after the upgradePro

Rewrite stored manifest maps the APIs, the way helm mapkubeapis does, and can be undone.

Questions

Does the check change the cluster?: No. It only reads.
Why aren't objects already in the cluster a problem?: The API server converts them. What breaks is whatever still writes or reads a removed version, so that is what the check looks for.
Which versions does it cover?: The version you pick, the next by default, plus the versions removed in the two releases after it.
Is it free?: The check is free; converted manifests and rewriting a release's stored manifest are part of Pro, free for 14 days, no card.

How the upgrade check works →

Use cases

Try it on your largest namespace.

Free for two clusters of any size. No account, no card: open KubeDrive and pick a context.