Skill Detail
Find deprecated Kubernetes APIs before cluster upgrades with kubent
Scan manifests and live clusters for removed or deprecated Kubernetes APIs before an upgrade window turns into an outage.
Runbooks & DiagnosticsMulti-Framework
Runbooks & Diagnostics
Multi-Framework
Security Reviewed
⭐ 3.7k GitHub stars
COPY SKILL INSTRUCTIONS (OPTIONAL)
npx skills add agentskillexchange/skills --skill find-deprecated-kubernetes-apis-before-cluster-upgrades-with-kubent
Uses the third-party skills CLI, not an ASE-owned installer. Check your agent’s compatibility. This copies instructions; complete the upstream tool setup below separately.
At a glance
Tools required
kubent binary, access to target Kubernetes manifests or cluster, target Kubernetes version context for upgrade analysis
Install & setup
Install kubent from the upstream release or package instructions, point it at the target manifests or cluster, and run the documented scan mode to surface deprecated or removed APIs before the upgrade window.
Author
doitintl
Publisher
Organization
Last updated
Apr 19, 2026
Quick brief
Use kubent when an agent needs to check manifests or a live cluster for APIs that will break in a target Kubernetes version before an upgrade starts. A user should invoke this instead of using Kubernetes normally when the job is upgrade-readiness analysis and remediation planning, not everyday cluster operations. The scope boundary is specific and skill-shaped: deprecated API discovery ahead of cluster upgrades, not a generic Kubernetes diagnostics or platform listing.