Kubernetes Removed API Lint

It reads the Kubernetes YAML open in your editor and marks every apiVersion and kind pair that Kubernetes has already removed, plus six annotations and fields that still parse but no longer do anything. Each finding names the release that removed the API, the date that release shipped, and the exact replacement to type. 36 rules, offline, no cluster access.

Platform and DevOps engineers who keep Helm charts, Kustomize bases or raw manifests in Git for clusters on EKS, GKE, AKS or self-managed Kubernetes, and who now accept manifests drafted by an AI assistant. It is aimed at the person who owns the upgrade ticket and has to prove the repository is ready before the control plane moves.

The chatbot is where the wrong line came from: batch/v1beta1 was valid for six years of its training data, so it defends the answer. kubent and Pluto are good, but they run after the fact against a cluster or a directory, need installing and a kubeconfig, and say nothing while you are typing the line in the editor.

Checking the file open in your editor is free forever, against all 36 rules, with no key and no account; the same engine also runs free in your browser on the product page. The licence covers a different job: sweeping every .yaml and .yml in the workspace and writing a dated Markdown report you keep and attach to the upgrade ticket.

A freelance Kubernetes platform engineer bills roughly 75 to 150 US dollars an hour on Upwork, and reading one repository for removed APIs is most of a working day. The licence is 29 dollars once, one key per person or CI seat, with a seven-day full refund. A failed apply mid-upgrade usually costs more than either.