eks-upgrade-check

Detect deprecated APIs and validate addon compatibility for Kubernetes/EKS upgrades.

1|Updated Jan 26, 2026

Search Tags:#compatibility #kubernetes #eks #upgrade #runbook #deprecated-apis #addon-verification

Ready to run

npx skills add https://github.com/filipemotta/devopsai-templates --skill eks-upgrade-check

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: eks-upgrade-check
Source: https://github.com/filipemotta/devopsai-templates/tree/main/skills/eks-upgrade
Command: npx skills add https://github.com/filipemotta/devopsai-templates --skill eks-upgrade-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Kubernetes and EKS upgrade planning is error-prone without proper compatibility checks, deprecated API detection, and actionable runbooks.

Core Features & Use Cases

Compatibility validation between current and target Kubernetes/EKS versions
Deprecated API detection using Pluto and Kubent
Addon/version compatibility checks and upgrade runbook generation
Pre-upgrade checks, risk assessment, and rollback planning
Use cases include planning production cluster upgrades and validating manifests

Quick Start

Plan and execute an EKS upgrade runbook by running guided checks and generating a pre-upgrade report.

Frequently Asked Questions about eks-upgrade-check

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

FAQPage Schema

How do I check for deprecated Kubernetes APIs before upgrading my EKS cluster?▼

To check for deprecated Kubernetes APIs before an EKS cluster upgrade, use tools like Pluto and Kubent to scan your current manifests. This process identifies removed or deprecated APIs early, allowing you to remediate manifests and generate an actionable upgrade runbook.

How do I validate EKS addon compatibility when planning a Kubernetes version upgrade?▼

Validating EKS addon compatibility during an upgrade involves checking your current addons against the target Kubernetes version. The process performs compatibility validation between versions to ensure addons are supported and produces a pre-upgrade risk assessment report.

What is included in an EKS upgrade runbook for production clusters?▼

An EKS upgrade runbook includes pre-upgrade checks, deprecated API detection, addon compatibility validation, and risk assessment. It provides an actionable upgrade plan and rollback planning to ensure production cluster upgrades are executed safely with minimal disruption.

Can I assess rollback risks before upgrading my EKS environment?▼

Yes, you can assess rollback risks before upgrading an EKS environment by generating a pre-upgrade risk assessment. This involves validating compatibility between your current and target Kubernetes versions and creating a structured rollback plan as part of your runbook.

Does EKS upgrade planning require checking compatibility between current and target Kubernetes versions?▼

Yes, EKS upgrade planning requires checking compatibility between your current and target Kubernetes versions. This validation ensures your manifests and addons are fully supported by the target version, preventing compatibility issues during the cluster upgrade process.

Why do deprecated API detection tools matter for Kubernetes upgrade planning?▼

Deprecated API detection tools matter for Kubernetes upgrade planning because they identify APIs that have been removed in the target version. Detecting these compatibility issues early prevents upgrade failures and ensures your manifests are updated before execution.