eks-upgrade-check

Evaluate EKS cluster upgrade readiness for a target Kubernetes version.

39|14|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/aws-samples/sample-apex-skills --skill eks-upgrade-check-aws-samples
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eks-upgrade-check
Source: https://github.com/aws-samples/sample-apex-skills/tree/main/skills/eks-upgrade-check
Command: npx skills add https://github.com/aws-samples/sample-apex-skills --skill eks-upgrade-check-aws-samples

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you determine whether an Amazon EKS cluster is safe to upgrade by exposing version, API, add-on, node, and workload risks before you proceed.

Core Features & Use Cases

  • Upgrade readiness assessment with scoring: Evaluates upgrade safety across version validation, breaking changes, deprecated APIs, add-on compatibility (including Karpenter), node readiness, workload upgrade risks, AWS Upgrade Insights, and plan generation.
  • Evidence-backed blockers and remediation: Produces a prioritized report with remediation guidance and pre-filled AWS CLI / kubectl-oriented actions, including a hard-blocker override that caps scores to prevent unsafe upgrades.
  • Graceful data-source fallback: Uses AWS CLI and kubectl when the EKS MCP server is unavailable, while still supporting richer EKS operations when MCP is enabled.

Quick Start

Ask the agent to run an EKS upgrade readiness assessment for your cluster and target Kubernetes version.

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 if my EKS cluster is ready for a Kubernetes version upgrade?

To check EKS upgrade readiness, run an automated assessment against your target Kubernetes version to validate breaking changes, deprecated APIs, and add-on compatibility. This scores readiness from 0-100 and generates a prioritized Markdown report with remediation commands.

What are common EKS upgrade blockers when updating to a newer Kubernetes version?

Common EKS upgrade blockers include usage of deprecated Kubernetes APIs, incompatible add-ons, and node workload drain risks. The assessment applies a hard-blocker override that caps the readiness score to prevent unsafe upgrades until these issues are remediated.

Do I need the EKS MCP server installed to assess Kubernetes upgrade readiness?

You do not need the EKS MCP server to assess Kubernetes upgrade readiness. The skill features graceful fallback to standard AWS CLI and kubectl connectivity, while supporting richer EKS operations when MCP is enabled.

How does Karpenter compatibility affect EKS cluster upgrade safety?

Karpenter compatibility directly affects EKS cluster upgrade safety because incompatible add-ons prevent successful version migrations. The readiness check evaluates Karpenter alongside standard add-ons to ensure workload drain risks and node readiness are safely managed.

What is the best way to identify deprecated APIs before upgrading my EKS cluster?

The best way to identify deprecated APIs is to run a live readiness check against your specified target Kubernetes version. It evaluates live cluster data to flag deprecated API usage and generates pre-filled kubectl and AWS CLI remediation commands.