eks-ingress-migrationlisted

# EKS Ingress Migration Skill ## Overview This skill assesses your live EKS cluster's current Ingress architecture and evaluates migration options. It discovers what ingress controllers are running, maps the routing topology, identifies risks, and presents the findings so your team can decide the best migration path. **This is an assessment tool, not a decision-maker.** The skill presents findings and options — the migration strategy and readiness decision belongs to the user's DevOps team. **Migration options assessed:** | Option | Status | Notes | |--------|--------|-------| | Gateway API (HTTPRoute + Gateway) | ✅ Assessed | Official Kubernetes successor to Ingress. AWS LB Controller supports it (L7 ≥ v2.14, L4 ≥ v2.13; built-in on EKS Auto Mode). | | AWS Load Balancer Controller (ALB Ingress) | ✅ Assessed | Stay on Ingress API but swap NGINX→ALB. Gets WAF, Cognito, Shield. | | AWS Transform (ATX) — Automated | ✅ Included | TD included. For customers with ATX access — fully automated manifest rewriting. | ## Workflow ``` Pre-flight → Assess (7 sections) → Current Architecture Topology → Dual Report (md + html) → Export Materials ``` 1. **Pre-flight** — Discover cluster, validate permissions 2. **Assessment** — Run 7 sections, collect findings and topology data 3. **Current Architecture** — Compile topology data into JSON for the HTML report's interactive 3D view (nodes, controllers, ingresses, services) 4. **Dual Report** — Automatically generate both: - **Markdo