gateway-api-migration

Coordinate Kubernetes ingress migration from NGINX to Gateway API.

10|2|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/qwedsazxc78/devops-ai-skill --skill gateway-api-migration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gateway-api-migration
Source: https://github.com/qwedsazxc78/devops-ai-skill/tree/main/skills/gateway-api-migration
Command: npx skills add https://github.com/qwedsazxc78/devops-ai-skill --skill gateway-api-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires yq, kustomize, python3, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill streamlines the migration of Kubernetes ingress resources from NGINX to Gateway API, enabling zero-downtime upgrades and improved scalability.

Core Features & Use Cases

  • Topology Discovery: Classifies ingress resources into master, minion, or standalone types.
  • Resource Generation: Creates Gateway, HTTPRoute, and related CRDs with environment-specific configurations.
  • Automated Validation: Checks cluster prerequisites, CRD versions, and resource integrity before deployment.
  • Use Case: Deploy a new Gateway API stack alongside existing ingress controllers, verify connectivity, and perform DNS cutover with minimal disruption.

Quick Start

Run the migration script with your repository path to generate all necessary resources, review the report, and proceed with DNS switch when ready.

Frequently Asked Questions about gateway-api-migration

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

FAQPage Schema
How do I migrate Kubernetes ingress resources from NGINX to Gateway API?

To migrate ingress to Gateway API, this Skill classifies existing NGINX resources, generates Gateway and HTTPRoute CRDs, and validates cluster prerequisites to ensure a smooth, reversible transition.

What is the best way to achieve zero-downtime upgrades when adopting Gateway API?

Zero-downtime Gateway API adoption is achieved through a side-by-side deployment strategy, allowing you to verify connectivity and perform a DNS cutover with minimal disruption once testing is complete.

Do I need kustomize and yq to automate Gateway API rollouts?

Yes, automating Gateway API rollouts requires kustomize, yq, and python3 to parse configurations, generate environment-specific resources, and coordinate the detailed deployment procedures.

How does cluster validation work before deploying Gateway API CRDs?

Cluster validation checks cluster prerequisites, CRD versions, and resource integrity before deployment, generating validation reports to assist operators in executing safe transitions.

Can I classify NGINX ingress topologies before generating HTTPRoute resources?

Yes, topology discovery classifies ingress resources into master, minion, or standalone types before generating HTTPRoute and Gateway resources, ensuring correct mapping and configuration.

How do I perform a DNS cutover after generating Gateway API resources?

After generating resources and verifying side-by-side connectivity, you perform a DNS switch to complete the cutover, ensuring high availability and security compliance throughout the process.