skills.rest
thc1006
thc1006COMMUNITY
Explore all skills by this author →
WebsiteGitHub

ingress-migration

Migrate Ingress configurations to Gateway API with Envoy Gateway resources.

1|Updated Feb 3, 2026
Search Tags:#kubernetes#gateway-api#envoy-gateway#httproute#ingress-migration#ingress-nginx-retirement
One-click install
npx skills add https://github.com/thc1006/dgx_spark_deploy_claude_k8s_skills --skill ingress-migration
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ingress-migration
Source: https://github.com/thc1006/dgx_spark_deploy_claude_k8s_skills/tree/main/skills/ingress-migration
Command: npx skills add https://github.com/thc1006/dgx_spark_deploy_claude_k8s_skills --skill ingress-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ingress configurations risk becoming deprecated as Ingress-NGINX retires; this skill guides automated migration to Gateway API for future-proof traffic routing.

Core Features & Use Cases

  • Automatic assessment and migration planning from ingress-nginx to Gateway API (Envoy Gateway).
  • Step-by-step migration guidance for TLS, routing, and load balancing.
  • Use case: teams migrating existing Ingress resources to Gateway API in clusters upgrading to Kubernetes 1.36+.

Quick Start

Run a guided migration flow to convert existing Ingress resources to Gateway API configurations.

Frequently Asked Questions about ingress-migration

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

FAQPage Schema
How do I migrate Ingress to Gateway API in Kubernetes?▼

To migrate Ingress to Gateway API, you can run a guided flow that automatically assesses existing configurations and generates a step-by-step migration plan using Envoy Gateway and HTTPRoute resources. This ensures reliable traffic routing during the transition.

What is the best way to handle Ingress-NGINX retirement for Kubernetes 1.36+?▼

Handling Ingress-NGINX retirement involves migrating deprecated configurations to Gateway API. This process converts existing routing and load-balancing rules to scalable resources like GatewayClass and HTTPRoute, ensuring ongoing traffic routing reliability.

Can I migrate TLS and load balancing configurations to Envoy Gateway?▼

Yes, you can migrate TLS and load balancing configurations to Envoy Gateway. The migration process provides step-by-step guidance to securely transfer these settings from Ingress resources to HTTPRoute, maintaining traffic reliability.

Does migrating Ingress to Gateway API require manual traffic routing updates?▼

Migrating Ingress to Gateway API does not require fully manual updates. The process applies an automated migration plan to convert existing Ingress resources into Gateway API configurations using Envoy Gateway, avoiding deprecated components effectively.

When do I need to use HTTPRoute and GatewayClass resources?▼

You need to use HTTPRoute and GatewayClass resources when upgrading Kubernetes clusters to future-proof traffic routing. They replace deprecated Ingress configurations, providing a scalable and automated routing structure using Envoy Gateway.

Related Skills

Explore More Software Engineering Skills→
alibabaalibaba
9.1k

nginx-to-higress-migration

Migrate ingress-nginx configurations to Higress while preserving routing, TLS, and security semantics.

Official
Advanced
thc1006thc1006

gateway-api

Configure and deploy Kubernetes Gateway API with Envoy Gateway.

Community
Intermediate
missBergmissBerg
3

eg-tls

Configure Envoy Gateway TLS termination, passthrough, and mTLS with cert-manager integration.

Community
Advanced
missBergmissBerg
3

eg-service-mesh

Integrate Envoy Gateway with Istio ambient or Cilium service mesh for unified ingress and east-west traffic management.

Community
Advanced