kubernetes-deprecation-check-and-upgrade

Detect deprecated Kubernetes APIs and map them to supported replacements.

3|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/infraspecdev/tesseract --skill kubernetes-deprecation-check-and-upgrade
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kubernetes-deprecation-check-and-upgrade
Source: https://github.com/infraspecdev/tesseract/tree/main/shield/skills/kubernetes/deprecation-check-and-upgrade
Command: npx skills add https://github.com/infraspecdev/tesseract --skill kubernetes-deprecation-check-and-upgrade

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill finds deprecated or removed Kubernetes APIs before they break upgrades, then tells you exactly how to replace them with supported versions.

Core Features & Use Cases

  • API Deprecation Auditing: Scans manifests, Helm templates, and Kustomize bases for deprecated Kubernetes resource versions.
  • Migration Guidance: Maps old APIs to replacements and highlights breaking field or behavior changes such as selector requirements or ingress path handling.
  • Upgrade Validation: Recommends schema checks, server-side dry runs, and Kind-based testing to confirm manifests work on the target cluster version.
  • Use Case: A platform engineer preparing a cluster upgrade can use this Skill to identify every manifest that will fail on the new version and plan the safest migration order.

Quick Start

Ask the Skill to review your Kubernetes manifests for a specific target version and return all deprecated APIs, required field changes, and validation steps.

Frequently Asked Questions about kubernetes-deprecation-check-and-upgrade

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find deprecated Kubernetes APIs before upgrading my cluster?

To find deprecated Kubernetes APIs before upgrading, scan your manifests, Helm templates, and Kustomize bases against the target version's deprecation table. This identifies removed resource versions and maps them to supported replacements to prevent upgrade failures.

What breaking changes happen when migrating deprecated Kubernetes APIs?

Migrating deprecated Kubernetes APIs introduces breaking field and behavior changes, such as new selector requirements or altered ingress path handling. You must cross-reference deprecation tables to identify these schema modifications and update your manifests accordingly.

Does this API deprecation check work with Helm templates and Kustomize bases?

Yes, the API deprecation check works with Helm templates and Kustomize bases. It audits these files for deprecated Kubernetes resource versions, ensuring your templated manifests and overlay configurations are safe for the target cluster version.

How do I validate migrated Kubernetes manifests against a new cluster version?

To validate migrated Kubernetes manifests against a new cluster version, perform schema validation, execute server-side dry runs, and conduct Kind-based testing. These steps confirm your manifests function correctly on the target Kubernetes version before deployment.

What is the best way to plan a Kubernetes upgrade safely?

The best way to plan a Kubernetes upgrade safely is to audit all manifests for deprecated APIs, map them to supported replacements, and apply schema validation and dry-run testing. This determines the safest migration order for your workloads.