Migrating to Gateway API: Ingress2Gateway 1.0 Unleashed
Ingress2Gateway exists to simplify the often complex migration from Ingress to Gateway API. As Kubernetes evolves, the need for a more modular and extensible API becomes clear. Ingress2Gateway acts as an assistant, helping teams confidently navigate this transition while addressing the challenges that arise from implementation-specific annotations and configurations.
How does it work? Ingress2Gateway translates Ingress resources and their associated annotations into the Gateway API format. It supports over 30 common annotations, ensuring that your configurations remain intact. The tool also warns you about any untranslatable configurations and offers suggestions for adjustments. To guarantee that the generated Gateway API behaves equivalently to your original Ingress-NGINX setup, it runs integration tests, giving you peace of mind during the migration process.
In production, you’ll want to install Ingress2Gateway easily using Go or Homebrew. For example, you can run go install github.com/kubernetes-sigs/ingress2gateway@v1.0.0 or brew install ingress2gateway. When you're ready to translate your manifests, use commands like ingress2gateway print --input-file my-manifest.yaml --providers=ingress-nginx > gwapi.yaml. Keep in mind that you can specify different emitters like agentgateway, envoy-gateway, or kgateway to customize your output. This flexibility is crucial for aligning with your specific architecture and needs.
Key takeaways
- →Install Ingress2Gateway using 'go install' or 'brew install'.
- →Translate Ingress resources with 'ingress2gateway print --input-file my-manifest.yaml'.
- →Utilize integration tests to verify behavioral equivalence with Ingress-NGINX.
- →Specify emitters for tailored output using the '--emitter' flag.
- →Support over 30 common annotations to ease the migration process.
Why it matters
Migrating to Gateway API can significantly enhance your Kubernetes networking capabilities, providing better modularity and extensibility. Ingress2Gateway streamlines this transition, reducing downtime and configuration errors.
Code examples
go install github.com/kubernetes-sigs/ingress2gateway@v1.0.0brew install ingress2gatewayingress2gateway print --input-file my-manifest.yaml,my-other-manifest.yaml --providers=ingress-nginx > gwapi.yamlWhen NOT to use this
The official docs don't call out specific anti-patterns here. Use your judgment based on your scale and requirements.
Want the complete reference?
Read official docsUnified observability — logs, uptime monitoring, and on-call in one place. Used by 50,000+ engineering teams to ship faster and sleep better.
Try Better Stack free →Seamlessly Access Private Git Repositories in EKS with Argo CD
Unlock the power of Argo CD by integrating it with private Git repositories hosted on AWS. Learn how to set up AWS CodeConnections to create a secure network path for your Git server, ensuring smooth deployment workflows.
Mastering Full Request and Response Logging on Amazon EKS
In a world where compliance is non-negotiable, capturing full request and response data is crucial. Learn how Envoy’s External Processing filter enables this without altering your application code.
Mastering EKS Control Plane Egress: Route Your Traffic with Precision
Amazon EKS now allows you to route Kubernetes control plane traffic through your own VPC, giving you greater control over egress traffic. By enabling CUSTOMER_ROUTED mode, you can ensure that API server calls follow your configured routes and security groups.
Get the daily digest
One email. 5 articles. Every morning.
No spam. Unsubscribe anytime.