Source

This page is generated from skills/eks-upgrade-check/references/upgrade-insights.md. Edit the source, not this page.

Vendored skill

This skill is sourced from eks-upgrade-check, also maintained by the APEX team.

AWS Upgrade Insights

Purpose

Retrieve and interpret official AWS EKS Upgrade Insights — pre-upgrade checks that AWS runs against your cluster.

How to Check

Step 1: Get All Insights

1. Call get_eks_insights with the cluster name
2. Filter for category UPGRADE_READINESS
3. Record each insight: ID, status, name, description

Step 2: Get Details for Non-Passing Insights

For any insight with status other than PASSING:

1. Call get_eks_insights with the specific insight_id
2. Record: detailed description, recommendation, affected resources

Step 3: Classify Findings

Insight Status	Severity
PASSING	NONE
WARNING	MEDIUM
ERROR	HIGH
UNKNOWN	LOW

Step 4: Cross-Reference with Other Sections

AWS Upgrade Insights often overlap with findings from other sections (deprecated APIs, add-on compatibility). When reporting:

• Note if an insight confirms a finding from another section
• Do NOT double-count in the score — the insight score is separate from other categories
• Highlight any insights that reveal issues NOT caught by other checks

Important Context for Users

AWS Upgrade Insights checks multiple versions ahead, not just the immediate target. For example, if upgrading from 1.30 → 1.31, AWS may flag deprecated APIs that are removed in 1.33. This is valuable forward-looking information but should not be confused with immediate blockers.

Explain this distinction clearly in the report:

• "Blocked for target version" = must fix before upgrading
• "Flagged by AWS for future version" = plan to fix, but not a blocker for this upgrade

Score Impact

Canonical scoring is defined in references/report-generation.md §Category 7. Quick reference: FAILING = 5 pts, ERROR = 3 pts, WARNING = 2 pts. Max category = 10 pts.